summaryrefslogtreecommitdiff
path: root/spec
AgeCommit message (Collapse)Author
2019-09-20Removed Scanf from the ruby repository.Hiroshi SHIBATA
2019-09-20Removed CMath from the ruby repository.Hiroshi SHIBATA
2019-09-20Allow calling a private accessor with `self.`Nobuyoshi Nakada
[Feature #11297] [Feature #16123] Notes: Merged: https://github.com/ruby/ruby/pull/2474
2019-09-20Added version guardNobuyoshi Nakada
[Feature #11297] [Feature #16123] Notes: Merged: https://github.com/ruby/ruby/pull/2474
2019-09-20Allow calling a private method with `self.`Dylan Thacker-Smith
This makes it consistent with calling private attribute assignment methods, which currently is allowed (e.g. `self.value =`). Calling a private method in this way can be useful when trying to assign the return value to a local variable with the same name. [Feature #11297] [Feature #16123] Notes: Merged: https://github.com/ruby/ruby/pull/2474
2019-09-18Fixed up ccbfb054b1dcd06d30924c4a83af1bac75d78c31Hiroshi SHIBATA
2019-09-18Fixed the rubocop warningsHiroshi SHIBATA
2019-09-18[bundler/bundler] Merge all `bundle check --path` specsDavid Rodríguez
And skip them all for bundler 3. https://github.com/bundler/bundler/commit/b88936cdc2
2019-09-18[bundler/bundler] Merge #7340Bundlerbot
7340: Fix bundle clean issue r=deivid-rodriguez a=deivid-rodriguez ### What was the end-user problem that led to this PR? The problem was that `bundle clean` is crashing under some conditions. ### What was your diagnosis of the problem? My diagnosis was that sometimes (when the bundle includes git sourced gems with extensions), it assumes that some paths exist, but they don't. ### What is your fix for the problem, implemented in this PR? My fix is to ignore those paths. ### Why did you choose this fix out of the possible options? I chose this fix because it fixes the issue. Fixes #7338. Co-authored-by: David Rodríguez <deivid.rodriguez@riseup.net> (cherry picked from commit b007fde67c77c1f15f13b97eda186644c2a2be04) https://github.com/bundler/bundler/commit/3766053507
2019-09-18[bundler/bundler] Fix remembered flag deprecation messageDavid Rodríguez
It was suggested a deprecated command as a fix. https://github.com/bundler/bundler/commit/e330a9a34f
2019-09-18[bundler/bundler] Add a spec for installing git deps after packaging w/o gitSamuel Giddins
https://github.com/bundler/bundler/commit/65351c58b8
2019-09-18[bundler/bundler] Revert "Add all platforms to lockfile by default"David Rodríguez
This reverts commit 3dc509e645abb497e4dc92a7c42be471ff87db0b. https://github.com/bundler/bundler/commit/b5766564fb
2019-09-18[bundler/bundler] Revert "Remove now meaningless warning"David Rodríguez
This reverts commit 00b095b98fe4bd44950beaf3bc9f1d91eac7b69e. https://github.com/bundler/bundler/commit/e93bce3b20
2019-09-18[bundler/bundler] Fix comments and messages to refer to https urlTakayuki Nakata
https://github.com/bundler/bundler/commit/a86b49f1b9
2019-09-18[bundler/bundler] Remove duplicated spec filterDavid Rodríguez
https://github.com/bundler/bundler/commit/b7fc6f4187
2019-09-18[bundler/bundler] Deprecate `--path` flag to `bundle check`David Rodríguez
https://github.com/bundler/bundler/commit/0a0e7cf5ec
2019-09-15Refine Timezone fixtureNobuyoshi Nakada
2019-09-09Make test-all and test-spec runnable on AndroidYusuke Endoh
Calling some syscall functions such as Dir.chroot causes SIGSYS instead of EPERM on Android. This change skips all tests that stops the test-suite run.
2019-09-08Improve Proc#to_s specsBenoit Daloze
2019-09-08Removed useless braces to suppress a warningNobuyoshi Nakada
2019-09-07armv7l and armv7l are the same platform, generalize to armv7Benoit Daloze
[Bug #16007]
2019-09-05Add `File.absolute_path?` (#2198)David Rodríguez
In order to check whether a path is absolute or not in a portable way. [Feature #15868]
2019-09-03Remove bad expectation in specJeremy Evans
This spec should not be checking where methods are defined, only that the method works as expected (returns a Lazy instance). Notes: Merged: https://github.com/ruby/ruby/pull/2421
2019-09-02Prohibit nul-separated glob pattern [Feature #14643] (#2419)Nobuyoshi Nakada
Notes: Merged-By: nobu <nobu@ruby-lang.org>
2019-09-01Ignore the all of warnings with inline_spec.rb of bundler examples.Hiroshi SHIBATA
2019-08-30Warn for keyword to last hash parameter when method has no optional/rest ↵Jeremy Evans
parameters Previously, there was no warning in this case, even though we will be changing the behavior in Ruby 3. Fixes [Bug #14130]
2019-08-30Fix a couple of bundler issues with keyword argument separationJeremy Evans
There are more issues than this, but hopefully this is enough to get make test-bundler passing in CI. Notes: Merged: https://github.com/ruby/ruby/pull/2395
2019-08-30Update specs to handle non-Symbols for keyword splats in 2.7Jeremy Evans
Also handle some warnings for behavior that will change in 3.0. Notes: Merged: https://github.com/ruby/ruby/pull/2395
2019-08-30spec/ruby/core/unboundmethod/bind_call_spec.rb: Add ruby_version_is guardYusuke Endoh
2019-08-30spec/ruby/core/unboundmethod/bind_call_spec.rb: AddedYusuke Endoh
For UnboundMethod#bind_call [Feature #15955] introduced in 002e592e0d67bb0271d16314a32380ad947c9ae9.
2019-08-29Fixed a comment [ci skip]Nobuyoshi Nakada
A range literal in conditional expression is turned into a flip-flop, as a Range object is never falsy and does not make a sense.
2019-08-29Revert "Remove warnings of flip-flop deprecation from tests and specs"Nobuyoshi Nakada
This reverts commit bf7a32d22079cc44eb19794e41d82b886d5d17b3. flip-flop is no longer deprecated. [Feature #5400]
2019-08-28Follows callback declaration updatesNobuyoshi Nakada
2019-08-27Fix rb_thread_create argument typeTakashi Kokubun
in response to the declaration change in e3fc30564e9466d6926f9d25a090dcf787bd5c33. Fixing the AppVeyor mswin CI failure: https://ci.appveyor.com/project/ruby/ruby/builds/26980881/job/2j6h1qwjnbc8cpop ref: https://github.com/ruby/ruby/pull/2404
2019-08-23Remove github_action_linux tag from bundler examples.Hiroshi SHIBATA
Maybe it has fixed at 5a384e2c08704dc7af9d8d3bdfc475eb8c0723aa Notes: Merged: https://github.com/ruby/ruby/pull/2399
2019-08-21The investigation is going on...Nobuyoshi Nakada
2019-08-21[bundler/bundler] Freeze time to avoid failures at midnightlolwut
Specify just a string set @built_at as nil before testing https://github.com/bundler/bundler/commit/578ec96c9c
2019-08-21[bundler/bundler] Share test fixtures with parallel_testsHiroshi SHIBATA
https://github.com/bundler/bundler/commit/a38161c5be
2019-08-21[bundler/bundler] Try to use RunTimeLogger for parallel_testsHiroshi SHIBATA
https://github.com/bundler/bundler/commit/faccc522d1
2019-08-21[bundler/bundler] Parallelize test suiteDavid Rodríguez
https://github.com/bundler/bundler/commit/23007cb107
2019-08-21[bundler/bundler] Fix a couple of typosDavid Rodríguez
https://github.com/bundler/bundler/commit/52b6b94068
2019-08-21[bundler/bundler] Remove the :ruby exclusion tagDavid Rodríguez
Our current set of specs is the same for all supported rubies, and we should keep it that way. https://github.com/bundler/bundler/commit/c9dc0f6f2c
2019-08-21[bundler/bundler] Remove another 1.8.7 specific bitDavid Rodríguez
https://github.com/bundler/bundler/commit/8c7942d2c6
2019-08-21[bundler/bundler] Remove old rubies stuff no longer neededDavid Rodríguez
https://github.com/bundler/bundler/commit/36fb3287f4
2019-08-20Investigation of a sporadic error at Github ActionsNobuyoshi Nakada
2019-08-20Fix some bundler specs (#2380)David Rodríguez
* These seem to consistenly pass already * Show actual command when running `make test-bundler` Current the setup command that installs the necessary gems for testing bundler was printed, but not the actual command that runs the tests. That was a bit confusing. * Borrow trick from setproctitle specs * A title that long doesn't get set sometimes No idea why, but the test doesn't need that the title is that long. * Fix most gem helper spec ruby-core failures * Fix the rest of the gem helper failures * Fix version spec by improving the assertion * Remove unnecessary `BUNDLE_RUBY` environment var We can use `RUBY` when necessary, and `BUNDLE_RUBY` is not a good name because bundler considers `BUNDLE_*` variables as settings. * Rename `BUNDLE_GEM` to `GEM_COMMAND` This is more descriptive I think, and also friendlier for bundler because `BUNDLE_` env variables are interpreted by bundler as settings, and this is not a bundler setting. This fixes one bundler spec failure in config specs against ruby-core. * Fix quality spec when run in core Use the proper path helper. * Fix dummy lib builder to never load default gems If a dummy library is named as a default gem, when requiring the library from its executable, the default gem would be loaded when running from core, because in core all default gems share path with bundler, and thus they are always in the $LOAD_PATH. We fix the issue by loading lib relatively inside dummy lib executables. * More exact assertions Sometimes I have the problem that I do some "print debugging" inside specs, and suddently the spec passes. This happens when the assertion is too relaxed, and the things I print make it match, specially when they are simple strings like "1.0" than can be easily be part of gem paths that I print for debugging. I fix this by making a more exact assertion. * Detect the correct shebang when ENV["RUBY"] is set * Relax assertion So that the spec passes even if another paths containing "ext" are in the load path. This works to fix a ruby-core issue, but it's a better assertion in general. We just want to know that the extension path was added. * Use folder structure independent path helper It should fix this spec for ruby-core. * Fix the last failing spec on ruby-core * Skip `bundle open <default_gem>` spec when no default gems
2019-08-18Skip open_spec.rb:L95 because ruby repo doesn't have json as default gems.Hiroshi SHIBATA
2019-08-18[bundler/bundler] Remove unnecessary requireDavid Rodríguez
https://github.com/bundler/bundler/commit/8ef571ed4e
2019-08-18[bundler/bundler] No need to activate the `fileutils` default gemDavid Rodríguez
The version we're vendoring actually relaxed this restriction back to 2.3.0+, so we can always use the vendored version. https://github.com/bundler/bundler/commit/d366cbfe5d
2019-08-18[bundler/bundler] Remove unnecessary rubygems monkeypatchDavid Rodríguez
Instead, make sure we always load the local copy of bundler during specs, and never end up using the default copy. https://github.com/bundler/bundler/commit/ac655ffeda
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-14 01:04:15 +0000