8000 [Feature #20187] Skip examples for bundled gems at Ruby 3.4 by hsbt · Pull Request #9960 · ruby/ruby · GitHub
[go: up one dir, main page]

Skip to content

[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

Closed
wants to merge 9 commits into from

Conversation

hsbt
Copy link
Member
@hsbt hsbt commented Feb 14, 2024

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 for test-spec.

Also see 5bf75c2

hsbt added 9 commits February 14, 2024 10:55
`.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/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
Copy link
Member

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.

@hsbt
Copy link
Member Author
hsbt commented Feb 14, 2024

I discussed this with @nurse. We will separate ruby/spec to two groups.

  1. core and library for default gems
  2. library for bundled gems

I will make test-spec for 1 and disable to load .bundle directory. After that, I will create new mspec definition for bundled gems like bigdecimal etc. test-bundled-gems invoke that new definition.

@hsbt hsbt closed this Feb 14, 2024
@hsbt hsbt deleted the skip-bundled-gems-spec branch February 14, 2024 09:26
@eregon
Copy link
Member
eregon commented Feb 14, 2024

That sounds good.

@eregon
Copy link
Member
eregon commented Feb 14, 2024

I would still like to understand what is a concrete problem with extract-gems as a dependency of test-spec (as mentioned in https://bugs.ruby-lang.org/issues/20187#note-7).
It seems simplest as on current master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0