-
Notifications
You must be signed in to change notification settings - Fork 22
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
Recent changes for v0.1.0.2 do not pass RubySpec #34
Comments
Failing specs for convenience:
|
This is already fixed at ruby/ruby@36f297e |
So that change will go into v0.1.0.3 and other maintenance releases? We need to get the security fix out for JRuby 9.3 ASAP, but the 2.7-only test and this regression have blocked us. |
There is no change in ruby/cgi repo. They are only in https://github.com/ruby/spec. |
Oh I see, then either @eregon or I will update JRuby's copy of the specs so we can move forward with the security release. |
Thank you for the help here! |
👍 Your welcome. We may move them to this repo from ruby/spec in the future. |
I would support moving library specs into the library repositories. 👍
|
The changes in v0.1.0.2 do not appear to pass RubySpec. Either the library needs to be fixed or the specs need to be updated.
See https://github.com/jruby/jruby/actions/runs/3535817028/jobs/5934245109 for an example job that failed on JRuby after updating to v0.1.0.2.
The text was updated successfully, but these errors were encountered: