chore: retry certain steps on TravisCI to get more stable builds #249
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.
While I'm still looking into ways of getting more stable Sauce tests
there is one simple trick that we can do to increase our chances
of getting stable builds, see:
http://blog.travis-ci.com/2013-05-20-network-timeouts-build-retries/
Of course this is more of a work-around than a proper solution
but I'm afraid that we might need tricks like this one given the
number of different network-connected machines involved in the
build process. This seems to be a conclusion from the Travis-CI guys
as well...