spike to fix intermittent CI failures #122
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
We may want to consider *not* caching anything. Other serde projects do not: - https://github.com/serde-rs/serde/blob/master/.travis.yml - https://github.com/serde-rs/json/blob/master/.travis.yml That said, this purges the entire target build directory to see if that resolves issues like in #121.
|
/cc @punkstarman this may have worked 😄. |
|
Thank you @efx for contributing this. This problem has been quite annoying and I will be glad to have a fix for it. Let's see how this holds up for now and I'll consider deactivating the cache altogether in the future. |
ghost
deleted the
punkstarman
pushed a commit
that referenced
this pull request
Jul 29, 2020
* fix intermittent CI failures
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.
We may want to consider not caching anything. Other serde projects do
not:
That said, this purges the entire target build directory to see if that
resolves issues like in Deserialize directly to vec #121.