aboutsummaryrefslogtreecommitdiffstats
path: root/spec
Commit message (Collapse)AuthorAgeFilesLines
* [EXPERIMENTAL] Make Module#name return a frozen StringJean Boussier2019-09-261-5/+19
| | | | | | * Always the same frozen String for a given Module or Class. * Avoids extra allocations whenever calling Module#name. * See [Feature #16150]
* [EXPERIMENTAL] Make Symbol#to_s return a frozen StringBenoit Daloze2019-09-261-0/+17
| | | | | | * Always the same frozen String for a given Symbol. * Avoids extra allocations whenever calling Symbol#to_s. * See [Feature #16150]
* Fix documentation for ENV.each to return ENVJeremy Evans2019-09-201-1/+1
| | | | | | | | Also have spec check that it returns ENV. Mostly from burdettelamar@yahoo.com (Burdette Lamar). Fixes [Bug #16164]
* Removed Scanf from the ruby repository.Hiroshi SHIBATA2019-09-208-160/+0
|
* Removed CMath from the ruby repository.Hiroshi SHIBATA2019-09-2036-835/+0
|
* Allow calling a private accessor with `self.`Nobuyoshi Nakada2019-09-202-1/+3
| | | | [Feature #11297] [Feature #16123]
* Added version guardNobuyoshi Nakada2019-09-201-4/+12
| | | | [Feature #11297] [Feature #16123]
* Allow calling a private method with `self.`Dylan Thacker-Smith2019-09-201-1/+1
| | | | | | | | | | 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]
* Fixed up ccbfb054b1dcd06d30924c4a83af1bac75d78c31Hiroshi SHIBATA2019-09-181-1/+1
|
* Fixed the rubocop warningsHiroshi SHIBATA2019-09-181-1/+1
|
* [bundler/bundler] Merge all `bundle check --path` specsDavid Rodríguez2019-09-181-25/+30
| | | | | | And skip them all for bundler 3. https://github.com/bundler/bundler/commit/b88936cdc2
* [bundler/bundler] Merge #7340Bundlerbot2019-09-181-27/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* [bundler/bundler] Fix remembered flag deprecation messageDavid Rodríguez2019-09-181-1/+1
| | | | | | It was suggested a deprecated command as a fix. https://github.com/bundler/bundler/commit/e330a9a34f
* [bundler/bundler] Add a spec for installing git deps after packaging w/o gitSamuel Giddins2019-09-181-0/+17
| | | | https://github.com/bundler/bundler/commit/65351c58b8
* [bundler/bundler] Revert "Add all platforms to lockfile by default"David Rodríguez2019-09-182-23/+5
| | | | | | This reverts commit 3dc509e645abb497e4dc92a7c42be471ff87db0b. https://github.com/bundler/bundler/commit/b5766564fb
* [bundler/bundler] Revert "Remove now meaningless warning"David Rodríguez2019-09-181-0/+19
| | | | | | This reverts commit 00b095b98fe4bd44950beaf3bc9f1d91eac7b69e. https://github.com/bundler/bundler/commit/e93bce3b20
* [bundler/bundler] Fix comments and messages to refer to https urlTakayuki Nakata2019-09-181-1/+1
| | | | https://github.com/bundler/bundler/commit/a86b49f1b9
* [bundler/bundler] Remove duplicated spec filterDavid Rodríguez2019-09-181-1/+1
| | | | https://github.com/bundler/bundler/commit/b7fc6f4187
* [bundler/bundler] Deprecate `--path` flag to `bundle check`David Rodríguez2019-09-181-0/+22
| | | | https://github.com/bundler/bundler/commit/0a0e7cf5ec
* Refine Timezone fixtureNobuyoshi Nakada2019-09-153-18/+39
|
* Make test-all and test-spec runnable on AndroidYusuke Endoh2019-09-093-3/+3
| | | | | | 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.
* Improve Proc#to_s specsBenoit Daloze2019-09-081-7/+9
|
* Removed useless braces to suppress a warningNobuyoshi Nakada2019-09-081-2/+2
|
* armv7l and armv7l are the same platform, generalize to armv7Benoit Daloze2019-09-071-1/+1
| | | | [Bug #16007]
* Add `File.absolute_path?` (#2198)David Rodríguez2019-09-051-0/+53
| | | | | In order to check whether a path is absolute or not in a portable way. [Feature #15868]
* Remove bad expectation in specJeremy Evans2019-09-031-1/+0
| | | | | This spec should not be checking where methods are defined, only that the method works as expected (returns a Lazy instance).
* Prohibit nul-separated glob pattern [Feature #14643] (#2419)Nobuyoshi Nakada2019-09-021-1/+7
|
* Ignore the all of warnings with inline_spec.rb of bundler examples.Hiroshi SHIBATA2019-09-011-1/+1
|
* Warn for keyword to last hash parameter when method has no optional/rest ↵Jeremy Evans2019-08-301-4/+12
| | | | | | | | | parameters Previously, there was no warning in this case, even though we will be changing the behavior in Ruby 3. Fixes [Bug #14130]
* Fix a couple of bundler issues with keyword argument separationJeremy Evans2019-08-301-3/+4
| | | | | There are more issues than this, but hopefully this is enough to get make test-bundler passing in CI.
* Update specs to handle non-Symbols for keyword splats in 2.7Jeremy Evans2019-08-305-150/+378
| | | | Also handle some warnings for behavior that will change in 3.0.
* spec/ruby/core/unboundmethod/bind_call_spec.rb: Add ruby_version_is guardYusuke Endoh2019-08-301-36/+38
|
* spec/ruby/core/unboundmethod/bind_call_spec.rb: AddedYusuke Endoh2019-08-301-0/+50
| | | | | For UnboundMethod#bind_call [Feature #15955] introduced in 002e592e0d67bb0271d16314a32380ad947c9ae9.
* Fixed a comment [ci skip]Nobuyoshi Nakada2019-08-291-1/+1
| | | | | | 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.
* Revert "Remove warnings of flip-flop deprecation from tests and specs"Nobuyoshi Nakada2019-08-293-15/+10
| | | | | | | | This reverts commit bf7a32d22079cc44eb19794e41d82b886d5d17b3. flip-flop is no longer deprecated. [Feature #5400]
* Follows callback declaration updatesNobuyoshi Nakada2019-08-284-11/+16
|
* Fix rb_thread_create argument typeTakashi Kokubun2019-08-271-1/+1
| | | | | | | | | | 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
* Remove github_action_linux tag from bundler examples.Hiroshi SHIBATA2019-08-232-2/+1
| | | | Maybe it has fixed at 5a384e2c08704dc7af9d8d3bdfc475eb8c0723aa
* The investigation is going on...Nobuyoshi Nakada2019-08-211-6/+0
|
* [bundler/bundler] Freeze time to avoid failures at midnightlolwut2019-08-211-2/+7
| | | | | | | | Specify just a string set @built_at as nil before testing https://github.com/bundler/bundler/commit/578ec96c9c
* [bundler/bundler] Share test fixtures with parallel_testsHiroshi SHIBATA2019-08-211-1/+1
| | | | https://github.com/bundler/bundler/commit/a38161c5be
* [bundler/bundler] Try to use RunTimeLogger for parallel_testsHiroshi SHIBATA2019-08-211-0/+5
| | | | https://github.com/bundler/bundler/commit/faccc522d1
* [bundler/bundler] Parallelize test suiteDavid Rodríguez2019-08-214-5/+22
| | | | https://github.com/bundler/bundler/commit/23007cb107
* [bundler/bundler] Fix a couple of typosDavid Rodríguez2019-08-212-2/+2
| | | | https://github.com/bundler/bundler/commit/52b6b94068
* [bundler/bundler] Remove the :ruby exclusion tagDavid Rodríguez2019-08-211-1/+0
| | | | | | | 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
* [bundler/bundler] Remove another 1.8.7 specific bitDavid Rodríguez2019-08-211-5/+0
| | | | https://github.com/bundler/bundler/commit/8c7942d2c6
* [bundler/bundler] Remove old rubies stuff no longer neededDavid Rodríguez2019-08-211-1/+1
| | | | https://github.com/bundler/bundler/commit/36fb3287f4
* Investigation of a sporadic error at Github ActionsNobuyoshi Nakada2019-08-201-0/+6
|
* Fix some bundler specs (#2380)David Rodríguez2019-08-2020-45/+66
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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
* Skip open_spec.rb:L95 because ruby repo doesn't have json as default gems.Hiroshi SHIBATA2019-08-181-1/+1
|
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-09 05:54:49 +0000