-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
JRUBY 9.2.0.0: Assertion Failure when Reporting RSpec Failure #5193
Comments
3c97f06 fixes this by removing the assertion. In parser valueNode can be null for a few cases like (a = ()). Amazed you do not see this on 1.7.x or 9.1.x as well with -ea. In the past I attempted to make all callers pass in implicitnilnode in null cases but it was never really robust. |
@enebo thanks! |
@original-brownbear @headius and I will be travelling next week and will be a bit spotty but keep the reports coming. We would love to see logstash be able to migrate much easier than the 9.1.x series was for you (ignore this bad grammar). |
@enebo @headius coming back to this: I tried upgrading to We'd be able/willing to contribute the code and if necessary the infrastructure for running those tests happily. |
I tried upgrading Logstash to
9.2.0.0
, unfortunately the RSpec doesn't seem to behave correctly there.When trying to report a test failure and having Java's
-ea
set, I run into below exception.Unfortunately this doesn't reproduce on every test failure. The failure is also reported correctly when Java assertions aren't enabled.
Unfortunately the best reproducer I can offer so far is to:
./gradlew rubyTests
The text was updated successfully, but these errors were encountered: