Skip to content
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

Fix JRuby builds #637

Merged
merged 17 commits into from
Jun 28, 2019
Merged

Fix JRuby builds #637

merged 17 commits into from
Jun 28, 2019

Conversation

mvz
Copy link
Contributor

@mvz mvz commented May 30, 2019

Summary

JRuby builds have been failing on master for a while. Make them pass.

Details

Note: Some parts of this pull request have been forward-ported from still.

  • Allow nested ruby processes more time to finish. This was the main reason for the build failures started by 9b78d1b, where a nested ruby process was introduced in the specs.
  • Do not start SimpleCov on JRuby, avoiding warnings about needed JRuby settings
  • Use our own aruba/config/jruby helper to set JRuby options
  • Set Java options on OSX (Java 9) to avoid illegal reflective access warnings
  • Do not require zsh for the tests
  • Do not build with JRuby 9.2.7.0 due to Backtrace set with set_backtrace is not dup'd properly in 9.2.7.0 jruby/jruby#5738 affecting Cucumber's scenario skipping method.
  • Clean up cucumber.yml which contained outdated assumptions about the RUBY_DESCRIPTION constant.
  • Remove a scenario that just tests Cucumber
  • Add tooling to print slowest scenarios
  • Do not run cucumber scenarios on OSX with JRuby 9.2.6.0, which consistently take too long to finish

Motivation and Context

If we want to support JRuby, builds should be green and build failures should be blocking for pull requests.

How Has This Been Tested?

Repeated running of the tests on Travis until everything passed.

Types of changes

  • Refactoring (cleanup of codebase without changing any existing functionality)

@mvz
Copy link
Contributor Author

mvz commented May 30, 2019

😞 😿

@mvz mvz force-pushed the fix-jruby-builds branch 2 times, most recently from 34a12af to 43914b1 Compare May 31, 2019 15:29
mvz added 15 commits June 15, 2019 13:25
Coverage is inaccurate unless running in debug mode
The Fuubar formatter will continue outputting even when a spec is
on-hold in a debugger like pry. Use the default formatter instead to
avoid this annoyance.
There's an issue with dup-ing an exception after its backtrace has been
set manually in JRuby 9.2.7.0. It should be resolved in 9.2.8.0 once that's
released.

See jruby/jruby#5738 for more details.
Linux Travis workers use an older version of Java that doesn't
understand the --add-opens flag.
The original timeout value (5) was sometimes too small to allow the process to
finish on Travis CI. A value of 30 should allow enough time. In general,
the process will end much more quickly.
@mvz mvz force-pushed the fix-jruby-builds branch from 1754dd6 to c40d251 Compare June 15, 2019 11:37
@mvz mvz force-pushed the fix-jruby-builds branch from c40d251 to 0ce4b7b Compare June 15, 2019 13:32
The cucumber scenarios take way too long at the moment. Disable those
for now.
@mvz mvz merged commit 3109b9e into master Jun 28, 2019
@mvz mvz deleted the fix-jruby-builds branch June 28, 2019 15:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant