Travis: Remove unused cache (prone to intermittent failures) #442
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
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.
Today, @isabelrios noticed a job that was marked as failed, even though every step passed. Based on this comment in travis-ci's issues, we might face unlogged cache failures.
This kind of error is usually not a problem, unless our shell scripts toggle
set -e(and we do here, for instance).After looking up the documentation, we actually don't use the cache anymore. It started when we had to move away from the container infrastructure. Like said here, we won't be able to go back to containers until a few more months.
Consequently, I propose to save some CPU time and make the jobs stronger by just removing the cache.
r? @fabricedesre