[CI] Use a consistent key for ccache caching in Short Integration Tests #5770
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
The default ccache action uses the current time as part of the key for caching. The main problem with this is that it can cause too many different cache entries, and can eject entries we want to be ejected. There isn't a reason to keep more than one copy of this cache around, so using a consistent key will cause it to eject itself. I put the name of the job in the key so that we can identify which entries belong to what jobs when we examine the cache. This change also updates to a newer version of the ccache action.
youngar
force-pushed
the
github-actions-ccache
branch
from
2dd31b3
to
818fc40
Compare
|
The new key evaluates to |
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.
The ccache action by default uses the current date and time as part of the key for caching. The main problem with this is that it can create too many different cache entries, and can eject entries we don't want to be ejected. There isn't a reason to keep more than one copy of this cache around, so using a consistent key will cause it to eject itself. I put the name of the job in the key so that we can identify which entries belong to what jobs when we examine the cache. This change also updates to a newer version of the ccache action.