Updated MRI and JRuby Travis build targets #218
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Merged
jdantonio
added a commit
that referenced
this pull request
Jan 1, 2015
Updated MRI and JRuby Travis build targets
| - 2.0.0 | ||
| - 1.9.3 | ||
| - ruby-head | ||
| - jruby-19mode | ||
| - jruby-1.7.17 |
There was a problem hiding this comment.
Because 1.7.18 is broken on Travis, too. It uses the fuzzy parameter and results in grabbing JRuby 9000. Specifying 1.7.17 is a recommended workaround.
There was a problem hiding this comment.
Now you know why there are two commits! :-)
My first commit set 1.7.18. I reasoning was the same as yours. Once that test run failed again I did some more Googling. That's when I found the 1.7.17 workaround. It's a very unintuitive issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With the release of MRI 2.2.0 and the impending release of JRuby 9000 it is time to update our Travis targets:
2.2.02.1.2to2.1.4jruby-19mode(TravisCI known issue)jruby-1.7.17in place of the brokenjruby-19modetarget