aboutsummaryrefslogtreecommitdiffstats
path: root/spec/bundler/support
Commit message (Collapse)AuthorAgeFilesLines
* Merge prepare version of Bundler 2.2.0Hiroshi SHIBATA2020-12-083-140/+2
|
* Merge bundler-2.2.0.rc.2Hiroshi SHIBATA2020-10-158-35/+79
|
* [rubygems/rubygems] https functionality was merged into `net/https`David Rodríguez2020-07-311-5/+0
| | | | https://github.com/rubygems/rubygems/commit/d81ce9e457
* Import remaining changesDavid Rodríguez2020-07-151-30/+48
| | | | | The "sync with commits" scripts failed to properly import these for some reason.
* [rubygems/rubygems] Easier way to find path to ruby binaryDavid Rodríguez2020-07-151-4/+1
| | | | https://github.com/rubygems/rubygems/commit/cdc201f5c4
* [rubygems/rubygems] No need to update remotesDavid Rodríguez2020-07-151-1/+0
| | | | | | Everything is already fetched locally. https://github.com/rubygems/rubygems/commit/9c304639b1
* [rubygems/rubygems] Git clone already takes care of thisDavid Rodríguez2020-07-151-1/+0
| | | | https://github.com/rubygems/rubygems/commit/6e0c28d3ab
* [rubygems/rubygems] Clone rubygems from the local repoDavid Rodríguez2020-07-151-1/+1
| | | | | | | | | | | | | It simplifies things and should avoid issues like the one we had where the master branch had a bad `.gitattributes` file and changing it on a PR would be disregarded. In order for this to work, we need to make sure to fetch all tags from the repository, so that they can properly be checked out later. This does not apply to the case of testing against `RGV=..`, since no extra cloning is needed there. https://github.com/rubygems/rubygems/commit/d088d936b8
* [rubygems/rubygems] Show also output from all commands on rubygems checkout ↵David Rodríguez2020-07-151-1/+9
| | | | | | errors https://github.com/rubygems/rubygems/commit/1fe24e471d
* [rubygems/rubygems] Remove `--quiet` flag to `git checkout`David Rodríguez2020-07-151-1/+1
| | | | | | | Since we don't show this output by default, it's better to be verbose in case we happen to need more info. https://github.com/rubygems/rubygems/commit/baa4ccf5a6
* [rubygems/rubygems] More portable PATH editionDavid Rodríguez2020-06-181-1/+1
| | | | https://github.com/rubygems/rubygems/commit/a6d50afad0
* s/sys_exec!/sys_execDavid Rodríguez2020-06-182-5/+5
|
* [rubygems/rubygems] Remove now unused "bang helpers"David Rodríguez2020-06-181-12/+0
| | | | https://github.com/rubygems/rubygems/commit/84e4c58e83
* [rubygems/rubygems] s/gem_command!/gem_commandDavid Rodríguez2020-06-182-5/+5
| | | | https://github.com/rubygems/rubygems/commit/f52733f6a4
* [rubygems/rubygems] Make helpers raise by defaultDavid Rodríguez2020-06-183-36/+27
| | | | https://github.com/rubygems/rubygems/commit/ade0c441d5
* [rubygems/rubygems] s/rails_fail/rails_pinned_to_old_activesupport/David Rodríguez2020-06-181-1/+1
| | | | | | | | | The `rails_fail` name is misleading because there's no specific reason why such a gem would need to fail. As a matter of fact, `bundle install`'ing a Genfile with only that dependency like the spec the previous commit adds is not expected to fail. https://github.com/rubygems/rubygems/commit/b947f40701
* Fix most exec specsDavid Rodríguez2020-06-151-0/+3
| | | | | | | | | The `gem_command` helper was failing to require `support/hax.rb`, which takes care of making sure rubygems actually picks up the right `ruby` executable under ruby-core setup (`ENV["RUBY"]`). This caused binstubs to be generated with a wrong shebang, and that caused `bundle exec` to not work. The error message was pretty confusing though due to https://bugs.ruby-lang.org/issues/16952.
* Fix `bin/rake spec:realworld:record`David Rodríguez2020-06-051-1/+0
| | | | | | | | | | | Previously it was failing and not recording. Also, the `BUNDLER_SPEC_FORCE_RECORD` environment variable was forcing every request to be recorded, including duplicated requests to the same endpoint. That meant the recorded `versions` file would be incorrect because it would contain the result of the last request, which would be `304 NOT MODIFIED`. So, to rerecord, delete cassettes and let them be recorded when needed.
* [rubygems/rubygems] Remove `forgotten_command_line_usages` from specsDavid Rodríguez2020-06-051-15/+0
| | | | | | | | Instead, use the non-deprecated option except when specifically testing deprecated CLI flags. In that case, pass the flag directly and limit the specs to `bundler < 3`. https://github.com/rubygems/rubygems/commit/3d5e186241
* [rubygems/rubygems] Make `forgotten_command_line_options` always "forget" ↵David Rodríguez2020-06-051-2/+0
| | | | | | options https://github.com/rubygems/rubygems/commit/4d39338670
* [rubygems/rubygems] Support running specs against a tarballDavid Rodríguez2020-06-052-7/+17
| | | | | | | | | | | | | When bundler specs are run from a ruby tarball (ruby-core does this), there's no git folder, so `git ls-files` fails. Support this case by making specs rely on the list of files from the bundler gemspec instead, and invert the spec that makes sure we ship the right set of files. As per the other quality specs, skip them in this case. https://github.com/rubygems/rubygems/commit/b28d5ec931
* [rubygems/rubygems] Remove unintended extra spaceDavid Rodríguez2020-06-051-1/+1
| | | | https://github.com/rubygems/rubygems/commit/1cc02930f3
* Revert "Fix a error in a `before(:suite)` hook"Hiroshi SHIBATA2020-06-051-18/+0
| | | | This reverts commit 67d2a715ca35090fbb3ab13df5b7348b1807dd47.
* Revert "Fix a failure in bundle version with version outputs the version ↵Hiroshi SHIBATA2020-06-051-2/+1
| | | | | | with build metadata" This reverts commit fcc8be0198a16cc5fa7d4827be0c781209b70f98.
* Fix a failure in bundle version with version outputs the version with build ↵Kazuhiro NISHIYAMA2020-05-251-1/+2
| | | | | | | | | | | | | | | | | | | | metadata ``` 1) bundle version with version outputs the version with build metadata Failure/Error: expect(out).to match(/\ABundler version #{Regexp.escape(Bundler::VERSION)} \(\d{4}-\d{2}-\d{2} commit #{COMMIT_HASH}\)\z/) expected "Bundler version 2.2.0.dev (2020-05-25 commit )" to match /\ABundler version 2\.2\.0\.dev \(\d{4}-\d{2}-\d{2} commit (?-mix:unknown|[a-fA-F0-9]{7,})\)\z/ Diff: @@ -1,2 +1,2 @@ -/\ABundler version 2\.2\.0\.dev \(\d{4}-\d{2}-\d{2} commit (?-mix:unknown|[a-fA-F0-9]{7,})\)\z/ +"Bundler version 2.2.0.dev (2020-05-25 commit )" Commands: $ /home/user/snapshot-master/ruby -I/home/user/snapshot-master/spec/bundler -r/home/user/snapshot-master/spec/bundler/support/artifice/fail.rb -r/home/user/snapshot-master/spec/bundler/support/hax.rb /home/user/snapshot-master/tmp/1/gems/system/bin/bundle version Bundler version 2.2.0.dev (2020-05-25 commit ) # $? => 0 ```
* Fix a error in a `before(:suite)` hookKazuhiro NISHIYAMA2020-05-251-0/+18
| | | | | | | | | | | https://github.com/ruby/actions/runs/703745101?check_suite_focus=true#step:16:27 ``` An error occurred in a `before(:suite)` hook. Failure/Error: contents = File.read(version_file) Errno::ENOENT: No such file or directory @ rb_sysopen - /home/runner/work/actions/actions/snapshot-master/tmp/1/bundler-2.2.0.dev/lib/bundler/version.rb ```
* Revert 1f011cccb16ca9e8ee378cb5a9d4c14459afd68cHiroshi SHIBATA2020-05-221-1/+0
|
* Sync Bundler PR #3624Hiroshi SHIBATA2020-05-2212-143/+214
|
* Skip some tests if extracted from tarball (again)Kazuhiro NISHIYAMA2020-05-191-0/+6
| | | | | | | | | Fix up previous commit ref 9aa75795f9f438d5c874d8e418c3c7cdd63024fa, 38002a8adbd98266426940d829429a30af0622a4, and 0e60b59d5884edb8f9aea023efd9b24f1ff02049
* Skip some tests if extracted from tarball (again)Kazuhiro NISHIYAMA2020-05-181-0/+4
| | | | ref 9aa75795f9f438d5c874d8e418c3c7cdd63024fa
* Use the gemspec in build_dir directlyHiroshi SHIBATA2020-05-142-5/+6
|
* Resolved the file path of gemspec for ruby core repositoryHiroshi SHIBATA2020-05-132-1/+5
|
* Added test_gems.rb for setup dependenciesHiroshi SHIBATA2020-05-131-1/+4
|
* Update the bundler version with master branchHiroshi SHIBATA2020-05-1326-372/+375
|
* Merge bundler-2.1.4Hiroshi SHIBATA2020-01-084-11/+21
|
* [bundler/bundler] Add ruby2_keywordsSutou Kouhei2020-01-013-3/+3
| | | | https://github.com/bundler/bundler/commit/29d932d72d
* Fixed test failures with gem command path on ruby core repo.Hiroshi SHIBATA2019-12-152-2/+6
|
* Prepare to release bundler-2.1.0Hiroshi SHIBATA2019-12-1512-82/+56
|
* Fix glob base in bundler.gemspecKazuhiro NISHIYAMA2019-11-191-1/+2
|
* Skip some tests if extracted from tarballKazuhiro NISHIYAMA2019-11-191-0/+9
|
* Merge Bundler 2.1.0.pre3 released versionHiroshi SHIBATA2019-11-137-16/+12
|
* Merge Bundler 2.1.0.pre.3Hiroshi SHIBATA2019-11-1149-105/+267
| | | | | | | | | | | | | | | Features: - Add caller information to some deprecation messages to make them easier to fix [#7361](https://github.com/bundler/bundler/pull/7361) - Reconcile `bundle cache` vs `bundle package` everywhere. Now in docs, CLI help and everywhere else `bundle cache` is the preferred version and `bundle package` remains as an alias [#7389](https://github.com/bundler/bundler/pull/7389) - Display some basic `bundler` documentation together with ruby's RDoc based documentation [#7394](https://github.com/bundler/bundler/pull/7394) Bugfixes: - Fix typos deprecation message and upgrading docs [#7374](https://github.com/bundler/bundler/pull/7374) - Deprecation warnings about `taint` usage on ruby 2.7 [#7385](https://github.com/bundler/bundler/pull/7385) - Fix `--help` flag not correctly delegating to `man` when used with command aliases [#7388](https://github.com/bundler/bundler/pull/7388) - `bundle add` should cache newly added gems if an application cache exists [#7393](https://github.com/bundler/bundler/pull/7393) - Stop using an insecure folder as a "fallback home" when user home is not defined [#7416](https://github.com/bundler/bundler/pull/7416) - Fix `bundler/inline` warning about `Bundler.root` redefinition [#7417](https://github.com/bundler/bundler/pull/7417)
* The investigation is going on...Nobuyoshi Nakada2019-08-211-6/+0
|
* [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-212-1/+9
| | | | https://github.com/bundler/bundler/commit/23007cb107
* [bundler/bundler] Fix a couple of typosDavid Rodríguez2019-08-211-1/+1
| | | | https://github.com/bundler/bundler/commit/52b6b94068
* Investigation of a sporadic error at Github ActionsNobuyoshi Nakada2019-08-201-0/+6
|
* Fix some bundler specs (#2380)David Rodríguez2019-08-203-4/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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
* [bundler/bundler] No need to activate the `fileutils` default gemDavid Rodríguez2019-08-181-8/+0
| | | | | | | 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
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-14 02:32:12 +0000