-
Notifications
You must be signed in to change notification settings - Fork 5.4k
[Feature #20187] Skip examples for bundled gems at Ruby 3.4 #9960
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By cl 10000 icking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
`.bundle` directory is for rspec examples and `test-bundled-gems`. ruby#6130 is focus to build bundled gems, not testing. It's accidentally side effect. Also see ruby@5bf75c2
…"' spec/ruby/library/bigdecimal/**/*_spec.rb
…"' spec/ruby/library/csv/**/*.rb
…"' spec/ruby/library/syslog/**/*.rb
…"' spec/ruby/library/base64/**/*_spec.rb
…"' spec/ruby/library/observer/**/*.rb
…"' spec/ruby/library/getoptlong/**/*.rb
…"' spec/ruby/library/abbrev/**/*.rb
spec/mspec/tool/wrap_with_guard.rb 'ruby_version_is ""..."3.4"' spec/ruby/core/rational/coerce_spec.rb spec/mspec/tool/wrap_with_guard.rb 'ruby_version_is ""..."3.4"' spec/ruby/library/bigmath/log_spec.rb spec/mspec/tool/wrap_with_guard.rb 'ruby_version_is ""..."3.4"' spec/ruby/core/integer/coerce_spec.rb and spec/ruby/core/time/at_spec.rb
1.coerce(2).map { |i| i.class }.should == [Integer, Integer] | ||
end | ||
end | ||
ruby_version_is ""..."3.4" do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This disables all Integer#coerce specs, it's not OK.
Same for Rational#coerce specs below.
I discussed this with @nurse. We will separate
I will make |
That sounds good. |
I would still like to understand what is a concrete problem with |
I added version guard to
ruby/spec
for Ruby 3.4 again.ruby/spec#1137 reverts all of commits and enable to run them again.
In background, maintaining bundled gems is out of scope ruby repository. We shouldn't keep their test code because they are not our responsibility. We only test them with
test-bundled-gems
for ruby Interpreter keep their support.#6130 makes to load bundled gems on
test-spec
. But it's accidentally changes fortest-spec
.Also see 5bf75c2