-
Notifications
You must be signed in to change notification settings - Fork 914
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
_dispatch_1 ArgumentError (JRuby 9.4.0, RSpec report) #7630
Comments
To clarify: I wonder if this is a form of incompatibility between JRuby 9.4.x and RSpec formatters, based on the stack trace. |
Interesting. We have rspec runs in our own repository that don't seem to have been affected. We'll have to dig into this deeper, with a newer version of rspec than we run in CI. |
Relates to jruby#7630, which may be a new incompatibility in rspec.
I pushed a PR that updates the rspec we use for CI. We'll see how that goes. @thbar If you have an example repository that reproduces the issue, let me know. |
@headius I do not have an example repository currently, but I will try to provide that! |
@thbar Definitely try 9.4.1.0 since I did fix multiple issues with ripper since 9.4.0.0 came out. |
@enebo I tried 9.4.1.0 and indeed it fixes the issue with the RSpec report. Sidenote: to install 9.4.1.0 with rbenv/ruby-build, I had to use a custom build since it's not already integrated there. I created
Issue solved, I will close the ticket, thanks @enebo & @headius! |
Relates to jruby#7630, which may be a new incompatibility in rspec.
Environment Information
jruby 9.4.0.0 (3.1.0) 2022-11-23 95c0ec159f OpenJDK 64-Bit Server VM 17.0.4.1+0 on 17.0.4.1+0 +jit [arm64-darwin]
Darwin Thibauts-MacBook-Air.local 21.6.0 Darwin Kernel Version 21.6.0: Sun Nov 6 23:29:57 PST 2022; root:xnu-8020.240.14~1/RELEASE_ARM64_T8101 arm64
Expected Behavior
While running a test suite (RSpec), the previous version of JRuby passed our test suite.
Actual Behavior
The test suite runs, gives a couple of failures (no problem on that), but the RSpec report is not rendered due to an exception which looks curious:
The text was updated successfully, but these errors were encountered: