summaryrefslogtreecommitdiff
path: root/spec/bundler
AgeCommit message (Collapse)Author
2020-03-29spec/bundler/other/platform_spec.rb: skip an attempt to simulate JRubyYusuke Endoh
2020-01-08Merge bundler-2.1.4Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/2822
2020-01-01[bundler/bundler] Add ruby2_keywordsSutou Kouhei
https://github.com/bundler/bundler/commit/29d932d72d
2019-12-25Merge Bundler 2.1.2 from bundler/bundler.Hiroshi SHIBATA
[Misc #16449][ruby-core:96458]
2019-12-18Merge bundler-2.1.1 from bundler/bundlerHiroshi SHIBATA
2019-12-15Delegate should be supported nowDavid Rodríguez
Since `did_you_mean` dropped its dependency on it. Notes: Merged: https://github.com/ruby/ruby/pull/2753
2019-12-15Fixed test failures with gem command path on ruby core repo.Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/2753
2019-12-15Prepare to release bundler-2.1.0Hiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/2753
2019-11-19Fix glob base in bundler.gemspecKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2683
2019-11-19Skip some tests if extracted from tarballKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2683
2019-11-19Allow unknown if ruby coreKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2683
2019-11-13Merge Bundler 2.1.0.pre3 released versionHiroshi SHIBATA
Notes: Merged: https://github.com/ruby/ruby/pull/2674
2019-11-11Merge Bundler 2.1.0.pre.3Hiroshi SHIBATA
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) Notes: Merged: https://github.com/ruby/ruby/pull/2668
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-01Ignore the all of warnings with inline_spec.rb of bundler examples.Hiroshi SHIBATA
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-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
2019-08-18[bundler/bundler] Don't use system bundler on this specDavid Rodríguez
If we use system bundler, when booting the "outermost" bundler process, bundler will save the path to the system bundler in BUNDLE_BIN_PATH, and use it again when booting the "innermost" bundler process (`bundle exec echo foo`). That means that second process will use the system bundler path again. However, we have `-rsupport/hax` in RUBYOPT, so that file will load from the local copy of bundler, and that file will load `bundler/version` from the project (not from system), because -Ilib is in the LOAD_PATH. That will end up causing redefinition errors because the same constant will be loaded from two different locations. In general, this is expected behavior, normally you will wrap the process with `Bundler.with_original_env` to reset the environment. However, the easiest fix here is to not use system bundler, because it's not really necessary and thus doesn't help the readability of the spec. https://github.com/bundler/bundler/commit/a3d72a34ab
2019-08-18[bundler/bundler] Fix spec using the deprecated `bundle config` modeDavid Rodríguez
https://github.com/bundler/bundler/commit/789dd1864f
2019-08-18[bundler/bundler] Remove a bunch of unneeded rubygems requiresDavid Rodríguez
https://github.com/bundler/bundler/commit/f9cb39e614
2019-08-18[bundler/bundler] Fix open default gem errorZehan Zhao
https://github.com/bundler/bundler/commit/792d724752
2019-08-18[bundler/bundler] Wrap `open` specs with a contextDavid Rodríguez
So I can add another context that doesn't run the `before` block. https://github.com/bundler/bundler/commit/06d0acc45a
2019-08-18[bundler/bundler] Prefer `before` to `before :each`David Rodríguez
https://github.com/bundler/bundler/commit/6678747fae
2019-08-18[bundler/bundler] Fix `bundle doctor` commandDavid Rodríguez
Previously `bundle doctor` would fail on any bundle that does not include git gems or plugins. This is because the previously used `Bundler.home` does not exist unless the bundle includes git gems or plugins. For example, with `bundle config set path .bundle`, it points to which does not exist unless this kind of gems exist in the Gemfile. The name `Bundler.home` is really unfortunate, it should probably be have more descriptive name, and be private. But for now I just want to make `bundle doctor` usable. https://github.com/bundler/bundler/commit/5531a18c1e
2019-08-18[bundler/bundler] Bundler displays a duplicate gem entries warning even if ↵David Stosik
gems only appear once per group https://github.com/bundler/bundler/commit/d18a83109e
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-21 17:40:21 +0000