JRuby Cucumber test failure: smelly.rb step with method_missing and define_method has exit status 143

[olleolleolle]

Running the Cucumber feature command_line_interface/minimum_score.feature:5 can fail on JRuby. See Failed build.

This is the output:

expected that command "rubycritic smelly.rb --no-browser" has exit status of "0", but has "143". (RSpec::Expectations::ExpectationNotMetError)

143 is SIGTERM. (Did the process get killed somehow?)

Speculation: Aruba has an exit_timeout setting, which is fixed at 30 in our features/support/env.rb. THAT could be the thing which sends the TERM signal to the rubycritic process, which is turn results in an exit status 143.

Background

• Failed build
• The line in the Cucumber feature which fails
• ...and the file-creating Step for that feature
• On my laptop with OS X all cucumber tests pass

See #222 for discussion.

[olleolleolle]

@tejasbubane Can we up the exit_timeout?

[etagwerker]

Cucumber has been removed from the test suite in #568, so this JRuby-on-Cucumber failure no longer applies. Closing.