From: "hsbt (Hiroshi SHIBATA)" <noreply@...>
Date: 2022-03-18T04:29:49+00:00
Subject: [ruby-core:107967] [Ruby master Bug#18643] test-bundler failed on ruby_3_1 CI

Issue #18643 has been updated by hsbt (Hiroshi SHIBATA).

Assignee set to hsbt (Hiroshi SHIBATA)
Status changed from Open to Assigned

https://github.com/ruby/ruby/pull/5608 will fix this issue.


----------------------------------------
Bug #18643: test-bundler failed on ruby_3_1 CI
https://bugs.ruby-lang.org/issues/18643#change-96916

* Author: znz (Kazuhiro NISHIYAMA)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
I think that this spec has failed since newer bundler released.

https://github.com/ruby/actions/runs/5590419280?check_suite_focus=true#step:18:199
```

       expected "Running `bundle update --bundler \"> 0.a\"` with bundler 2.3.7\nHTTP GET https://index.rubygems.org/...ctions/actions/snapshot-ruby_3_1/tmp/4/gems/system/specifications/rack-1.2.gemspec\nBundle updated!" to include "Using bundler 2.3.7\n"
       Diff:
       @@ -1,19 +1,37 @@
       -Using bundler 2.3.7\n
       +Running `bundle update --bundler "> 0.a"` with bundler 2.3.7
       +HTTP GET https://index.rubygems.org/versions
       +HTTP 200 OK https://index.rubygems.org/versions
       +Fetching gem metadata from https://rubygems.org/
       +Looking up gems ["bundler"]
       +HTTP GET https://index.rubygems.org/info/bundler
       +HTTP 200 OK https://index.rubygems.org/info/bundler
       +Updating bundler to 2.3.9.
       +Fetching bundler 2.3.9
       +Installing bundler 2.3.9
       +Running `bundle update --bundler "> 0.a"` with bundler 2.3.9
       +Found no changes, using resolution from the lockfile
       +Using bundler 2.3.9
       +0:  bundler (2.3.9) from /home/runner/work/actions/actions/snapshot-ruby_3_1/tmp/4/gems/system/specifications/bundler-2.3.9.gemspec
       +Using prints_loaded_gems 1.0
       +0:  prints_loaded_gems (1.0) from /home/runner/work/actions/actions/snapshot-ruby_3_1/tmp/4/gems/system/specifications/prints_loaded_gems-1.0.gemspec
       +Using rack 1.2
       +0:  rack (1.2) from /home/runner/work/actions/actions/snapshot-ruby_3_1/tmp/4/gems/system/specifications/rack-1.2.gemspec
       +Bundle updated!
     # ./spec/bundler/commands/binstubs_spec.rb:229:in `block (5 levels) in <top (required)>'
     # ./spec/bundler/spec_helper.rb:101:in `block (4 levels) in <top (required)>'
     # ./spec/bundler/spec_helper.rb:101:in `block (3 levels) in <top (required)>'
     # ./spec/bundler/support/helpers.rb:350:in `block in with_gem_path_as'
     # ./spec/bundler/support/helpers.rb:364:in `without_env_side_effects'
     # ./spec/bundler/support/helpers.rb:345:in `with_gem_path_as'
     # ./spec/bundler/spec_helper.rb:100:in `block (2 levels) in <top (required)>'
```

It can reproduce with a small example.

Spec expects 3.0's behavior:

```
$ rbenv local 3.0.3
$ bundle init
Writing new Gemfile to /tmp/x/Gemfile
$ bundle i
The Gemfile specifies no dependencies
Resolving dependencies...
Bundle complete! 0 Gemfile dependencies, 1 gem now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
$ bundle update --bundler "> 0.a"
The Gemfile specifies no dependencies
Bundle updated!
$
```

Actual 3.1's behavior:
```
$ rbenv local 3.1.1
$ bundle init
Writing new Gemfile to /tmp/x/Gemfile
$ bundle i
The Gemfile specifies no dependencies
Resolving dependencies...
Bundle complete! 0 Gemfile dependencies, 1 gem now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
$ bundle update --bundler "> 0.a"
Fetching gem metadata from https://rubygems.org/.
The Gemfile specifies no dependencies
Bundle updated!
$
```

I'm not sure which is expected behavior: spec's or changed implementation.




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>