-
Notifications
You must be signed in to change notification settings - Fork 725
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
With the 2014/12/29 rollout, JRuby is defaulting to jruby-head #3067
Comments
cc @mpapis, is this maybe due to a change in JRuby or is this a bug on our end? |
To test with JRuby 1.7.18, one needs to uninstall the existing install, then re-install 1.7.18 separately; e.g., before_install:
- rvm uninstall jruby
- rvm use jruby-1.7.18 --install I am not sure if using JRuby in the 1.8 mode is feasible, and I see that this is quite problematic for a build matrix containing JRuby. |
In essence, our cookbook runs:
But apparently with this, we end up with travis@debug-BanzaiMan-playing-around-ruby-1419878735:~/.rvm/rubies$ cd jruby-1.7.18-d19
travis@debug-BanzaiMan-playing-around-ruby-1419878735:~/.rvm/rubies/jruby-1.7.18-d19$ ./bin/jruby -v
jruby: warning: unknown property jruby.cext.enabled
jruby 9.0.0.0-SNAPSHOT (2.2.0p0) 2014-12-26 ff30b40 Java HotSpot(TM) 64-Bit Server VM 24.72-b04 on 1.7.0_72-b14 +jit [linux-amd64] |
Or, you can specify an older version of JRuby (1.7.17, say) in |
Specify a version for JRuby as per: travis-ci/travis-ci#3067
Specify a version for JRuby as per: travis-ci/travis-ci#3067 Using version 1.7.18 would require uninstalling and reinstalling JRuby (see thread above) which would be done for every entry in the build matrix, even the non-JRuby ones. So use 1.7.17 for now.
* somehow jruby19 went on to use 9k...
Due to travis-ci/travis-ci#3067 and rvm/rvm#3242, Travis currently using JRuby HEAD, which doesn't play well with our test suite.
RVM issue is fixed, but waiting for a release. |
Link to the issue: travis-ci/travis-ci#3067
It seems that defining `jruby` in .travis.yml already runs JRuby 9000. See https://travis-ci.org/rom-rb/rom/jobs/45789302#L102 This reverts commit dfd264f.
released RVM |
Building image now. Shooting for Wednesday (January 7) release. |
https://travis-ci.org/rspec/rspec-support/jobs/45770207#L544 See travis-ci/travis-ci#3067 Per http://docs.travis-ci.com/user/ci-environment/ Use -Xcompat.version=2.0 per `jruby --properties` as `--2.0` wasn't being respected
https://travis-ci.org/rspec/rspec-support/jobs/45770207#L544 See travis-ci/travis-ci#3067 Per http://docs.travis-ci.com/user/ci-environment/ Use -Xcompat.version=2.0 per `jruby --properties` as `--2.0` wasn't being respected
https://travis-ci.org/rspec/rspec-support/jobs/45770207#L544 See travis-ci/travis-ci#3067 Per http://docs.travis-ci.com/user/ci-environment/ Use -Xcompat.version=2.0 per `jruby --properties` as `--2.0` wasn't being respected
https://travis-ci.org/rspec/rspec-support/jobs/45770207#L544 See travis-ci/travis-ci#3067 Per http://docs.travis-ci.com/user/ci-environment/ Use -Xcompat.version=2.0 per `jruby --properties` as `--2.0` wasn't being respected Note that script/functions.sh declares # idea taken from: http://blog.headius.com/2010/03/jruby-startup-time-tips.html export JRUBY_OPTS="${JRUBY_OPTS} -X-C" # disable JIT since these processes are so short lived
https://travis-ci.org/rspec/rspec-support/jobs/45770207#L544 See travis-ci/travis-ci#3067 Per http://docs.travis-ci.com/user/ci-environment/ Use -Xcompat.version=2.0 per `jruby --properties` as `--2.0` wasn't being respected Note that script/functions.sh declares # idea taken from: http://blog.headius.com/2010/03/jruby-startup-time-tips.html export JRUBY_OPTS="${JRUBY_OPTS} -X-C" # disable JIT since these processes are so short lived
Will be deployed at 15:00 UTC on 2015-01-07. http://docs.travis-ci.com/user/build-environment-updates/2015-01-07/ |
https://travis-ci.org/rspec/rspec-support/jobs/45770207#L544 See travis-ci/travis-ci#3067 Per http://docs.travis-ci.com/user/ci-environment/ Travis sets JRUBY_OPTS="--server -Dcext.enabled=false -Xcompile.invokedynamic=false" but current JRuby throws warnings when passed -Dcext.enabled Until that is fixed, it is sensible to just set JRUBY_OPTS="--server -Xcompile.invokedynamic=false" It's common to modify JRUBY_OPTS in travis projects, and in fact script/functions.sh modimodimodimodifies it! # idea taken from: http://blog.headius.com/2010/03/jruby-startup-time-tips.html export JRUBY_OPTS="${JRUBY_OPTS} -X-C" # disable JIT since these processes are so short lived Use -Xcompat.version=2.0 per `jruby --properties` in place of `--2.0`, which wasn't being respected
https://travis-ci.org/rspec/rspec-support/jobs/45770207#L544 See travis-ci/travis-ci#3067 Per http://docs.travis-ci.com/user/ci-environment/ Travis sets JRUBY_OPTS="--server -Dcext.enabled=false -Xcompile.invokedynamic=false" but current JRuby throws warnings when passed -Dcext.enabled Until that is fixed, it is sensible to just set JRUBY_OPTS="--server -Xcompile.invokedynamic=false" It's common to modify JRUBY_OPTS in travis projects, and in fact script/functions.sh modifies it! # idea taken from: http://blog.headius.com/2010/03/jruby-startup-time-tips.html export JRUBY_OPTS="${JRUBY_OPTS} -X-C" # disable JIT since these processes are so short lived Use -Xcompat.version=2.0 per `jruby --properties` in place of `--2.0`, which wasn't being respected
These failures were fixed in: travis-ci/travis-ci#3067 Change-Id: If4eaf60977ef3203af8cf1e686c9b2dc85555388 Reviewed-on: http://gerrit.causes.com/45586 Reviewed-by: Shane da Silva <shane.dasilva@brigade.com> Tested-by: jenkins <jenkins@brigade.com>
travis-ci/travis-ci#3067 has been fixed.
" This reverts commit 20e0cd0. Conflicts: .travis.yml
" This reverts commit ca09c16.
This has been rolled out. |
See, for example: https://travis-ci.org/BanzaiMan/travis_production_test/jobs/45377947#L104
To get around this, please specify an older version of JRuby (e.g., 1.7.17).
The text was updated successfully, but these errors were encountered: