Workaround for Travis bug #2290
Merged
Conversation
This file contains 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
|
If we're allowing failures in 2.1, why also modify the |
|
@parkr I found this decision in others people commits. Ruby 2.1.1, which is chosen if you set 2.1, has a regretion, so they don’t trust 2.1. Jekyll doesn’t fail at 2.1.1. Should I switch the version back and allow failures for 2.1.0? Or just leave 2.1 without allowing failures? |
parkr
added a commit
that referenced
this pull request
May 3, 2014
| @@ -4,7 +4,7 @@ install: | |||
| - script/rebund download | |||
| - travis_retry bundle install --path vendor/bundle | |||
| rvm: | |||
| - 2.1.0 | |||
| - 2.1.1 | |||
There was a problem hiding this comment.
During the latest build environment updates Travis switched Ruby 2.1.0 to 2.1.1 at 04:00 UTC on the 30th of April. I think Jekyll can switch to Ruby 2.1.1 too. It’s not a workaround anymore, but a regular upgrade.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Switch Ruby version from 2.1.0 to 2.1 until fixed travis-ci/travis-ci#2220