travis workarounds #286
Merged
travis workarounds #286
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
|
💯 great fix @srenatus and this makes the whole tests a lot faster. so cool. |
|
😍 |
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.
builds are green again! yay \o/
This is what happened, today travis started routing 50% of the precise-based legacy builds to a new infrastructure (incl. new versions of things). Switched to Trusty since fixing the gem issue brought up an issue with installing lxc in this new infrastructure, so I switched us to that.
References:
services: - docker+ build matrixes can cause build routing issues on GCE travis-ci/travis-ci#5142 (comment)