Use run_id in ccache key to prevent concurrent save conflicts#50
Merged
Conversation
A Dockerfile-hash key is identical across all concurrent PRs and matrix jobs sharing the same Dockerfile, causing "Unable to reserve cache" races. Using run_id makes the primary key unique per run so saves never collide. restore-keys still warm up from the most recent cache for each matrix slot. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or 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
1 participant
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.
Summary
github.run_idmakes the primary key unique per run, so saves never colliderestore-keysstill warm up from the most recently saved cache for each matrix slot, then fall back to any slotTest plan
Cache restored from key: ccache-Linux-idf-...)🤖 Generated with Claude Code