Repository navigation
Conversation
fingolfin
added
release notes: not needed
A pull request's ccache entries can be restored only by later runs of the same pull request, and those rarely exist: 26 of the 35 pull requests tested since 2026-10-15 had a single CI run. Even then, master's cache, which every first run restores, already gives 97-99% ccache hits. So these entries, 9.4 of the 10.6 GB in the repository's Actions cache, serve almost nobody. Store the cache only from branch runs: pushes to master and stable-*, and the nightly schedule. Pull request runs keep restoring their base branch's cache through the existing fallback key; one that changes build rules or widely included headers now recompiles those parts on each push. Tag runs stop storing as well, since no other ref can restore their caches either. Assisted-by: Generative AI
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #6766 +/- ##
==========================================
+ Coverage 79.67% 79.70% +0.02%
==========================================
Files 684 684
Lines 295464 295464
Branches 8656 8656
==========================================
+ Hits 235421 235492 +71
+ Misses 58217 58145 -72
- Partials 1826 1827 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
fingolfin
force-pushed
the
mh-claude/ci-ccache-no-pr-save
branch
from
October 17, 2026 15:49
a49809f to
785778d
Compare
This branch has not been deployed
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.
A pull request's ccache entries can be restored only by later runs of the same pull request, and those rarely exist: 26 of the 35 pull requests tested since 2026-10-15 had a single CI run. Even then, master's cache, which every first run restores, already gives 97-99% ccache hits. So these entries, 9.4 of the 10.6 GB in the repository's Actions cache, serve almost nobody.
Store the cache only from branch runs: pushes to master and stable-*, and the nightly schedule. Pull request runs keep restoring their base branch's cache through the existing fallback key; one that changes build rules or widely included headers now recompiles those parts on each push. Tag runs stop storing as well, since no other ref can restore their caches either.
Assisted-by: Generative AI