Disable C++ trap caching for CodeQL runs #640
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
Trap caches aren't cleaned up even though the cleanup var is set. What's more, they should only ever be used for scheduled (i.e., weekly) runs on the main branch. This is another attempt at preventing cache churn. If it doesn't work, I suppose the only alternative is disabling it for topic branches...
rdw-software
force-pushed
the
codeql-cache-churn
branch
from
5f53a41 to
6828787
Compare
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.
Trap caches aren't cleaned up even though the cleanup var is set. What's more, they should only ever be used for scheduled (i.e., weekly) runs on the main branch. This is another attempt at preventing cache churn. If it doesn't work, I suppose the simplest alternative is altogether disabling it for topic branches...? (Needs more research)