-
Notifications
You must be signed in to change notification settings - Fork 79
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 clicking “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
Test suite is going to be broken with Ruby 3.3 #190
Comments
4 tasks
One would thought that this could be simple to fix:
But that is not the case unfortunately. Hopefully it will work in the future: rubygems/rubygems#7203 |
voxik
added a commit
to voxik/childprocess
that referenced
this issue
Dec 20, 2023
`rubygems/mock_gem_ui` was removed in RubyGems 3.5+: rubygems/rubygems#6623 Luckily, othe PR allowed to use standard RSpec methods for `$stdout` testing: rubygems/rubygems#7203 Fixes enkessler#190
voxik
added a commit
to voxik/childprocess
that referenced
this issue
Dec 20, 2023
`rubygems/mock_gem_ui` was removed in RubyGems 3.5+: rubygems/rubygems#6623 Luckily, other PR allowed to use standard RSpec methods for `$stdout` testing: rubygems/rubygems#7203 Fixes enkessler#190
sds
pushed a commit
that referenced
this issue
Dec 21, 2023
`rubygems/mock_gem_ui` was removed in RubyGems 3.5+: rubygems/rubygems#6623 Luckily, other PR allowed to use standard RSpec methods for `$stdout` testing: rubygems/rubygems#7203 Fixes #190
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is caused by:
rubygems/rubygems@eaa315b
ruby/ruby@7477284
I wish #178 / #182 landed soon to help address such issues.
The text was updated successfully, but these errors were encountered: