Invalidate Linux build caches more agressively #8031
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 run Linux CI on regular GitHub Action runners, which have ~30GB of disk space. This is nothing for Rust builds and, due to Cargo.lock perturbations, we tend to accumulate enough artifacts to fill the disk entirely since `restore-keys` alowed to keep the cache for different lockfiles. Instead, try to invalidate the cache more aggressively (which will cost us more frequent ~30min Linux CI runs) to see how this will work in comparison.
cla-bot
bot
added
the
cla-signed
|
Further options to consider:
|
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 run Linux CI on regular GitHub Action runners, which have ~30GB of disk space. This is nothing for Rust builds and, due to Cargo.lock perturbations, we tend to accumulate enough artifacts to fill the disk entirely since
restore-keysallowed to keep the cache for different lockfiles.Instead, try to invalidate the cache more aggressively (which will cost us more frequent ~30min Linux CI runs) to see how this will work in comparison.
Release Notes: