diff options
| author | David RodrÃguez <deivid.rodriguez@riseup.net> | 2024-11-28 22:32:14 +0100 |
|---|---|---|
| committer | git <svn-admin@ruby-lang.org> | 2024-11-29 15:29:32 +0000 |
| commit | 8b7516438100ff379e92ebc2b524cb9c16f3392c (patch) | |
| tree | f2feb29b4650713831879cef49de59330f4deee2 /spec/ruby | |
| parent | ee7ff4a12b9eefaeced9b6da52f7b21317ab595c (diff) | |
[rubygems/rubygems] Unify specs testing Bundler.setup failing behavior
They had slightly different behavior in Bundler 2 and Bundler 3 because
Bundler 3 will auto-clean after `bundle install`, so one of them system
installed gems won't be present when `Bundler.setup` fails.
We can unify the specs by moving installing system gems to _after_
`bundle install`, so the behavior in both cases is the same. Also, only
this spec actually needs these gems installed, so we can move that from
the `before` block to the body of the spec.
https://github.com/rubygems/rubygems/commit/b7251ec9c6
Diffstat (limited to 'spec/ruby')
0 files changed, 0 insertions, 0 deletions