-
-
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
NoMethodError: undefined method `on_kwrest_param' #5209
Comments
I think this is because there is no entry for |
@twalpole yep. You were right that we were missing that entry in parser event table. |
@enebo Great - any chance of there being a 9.2.0.x fix release with this in? or does it really need to wait for the |
@twalpole we should get a 9.2.1.0 probably beginning of next week to do a fast turn around point release. Some travel also interfered with us getting more fixed but we want to address all recently reported issues to keep the momentum up. |
@enebo Sounds good, thanks for the info. |
Is there a timeline for when this release will be available? |
RSpec's output formatter breaks on jruby-9.2.0.0 because of a bug in that jruby version (jruby/jruby#5209). This causes failures reporting test failures in test assertions which are formatted in certain ways. This prevents you from finding out what the test failure actually was. To avoid that kind of problem debugging test failures, bump up the tested jruby version to 9.2.1.0, which included a fix for that bug.
RSpec's output formatter breaks on jruby-9.2.0.0 because of a bug in that jruby version (jruby/jruby#5209). This causes failures reporting test failures in test assertions which are formatted in certain ways. This prevents you from finding out what the test failure actually was. To avoid that kind of problem debugging test failures, bump up the tested JRuby version. JRuby 9.2.1.0 included a fix for that bug, but isn't supported by circleci, so using 9.2.2.0.
RSpec's output formatter breaks on jruby-9.2.0.0 because of a bug in that jruby version (jruby/jruby#5209). This causes failures reporting test failures in test assertions which are formatted in certain ways. This prevents you from finding out what the test failure actually was. To avoid that kind of problem debugging test failures, bump up the tested JRuby version. JRuby 9.2.1.0 included a fix for that bug, but isn't supported by circleci, so using 9.2.2.0.
JRuby version
9.2.0.0
. Using Capybara3.2.1
and rspec3.7.0
. The following code:Blows up with the following:
If I remove the
, driver: :rack_test
argument, it works fine.I'm not sure whether I'm doing something wrong, whether this is a bug in JRuby or anything at all, just thought to report here. :) Please tell me if you need more information.
The text was updated successfully, but these errors were encountered: