Repository navigation
ci: lower the self-hosted ccache cap to 60G - #1671
Merged
Merged
Conversation
The cache filled the 120G cap (112G measured 2026-10-28) and /home was down to 57G free, with a game server and its database now on the same box. 60G still holds two to three generations of every Linux flag set. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 15 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
Lowers the persistent ccache cap on the self-hosted Linux runners from 120G to 60G. The cap is still set in one place only (
.github/actions/setup-linux-build/action.yml).Why
The worst case the 120G comment planned for has happened. Measured 2026-10-28:
G= 10^9)/home/homeA full
/hometakes out all four runner accounts and the login.60G still holds two to three generations of every Linux flag set (~20-26 GB per generation, measured 2026-09-13), so consecutive commits keep hitting. Only older generations get evicted sooner.
What changes
--max-size=60Ginstead of120G, plus the measurement in the comment above it.docs/agent-rules/self-hosted-ccache-slot-multiplier.md.The first self-hosted job after the merge re-asserts the cap, and ccache trims the cache down to it. Expect a lower hit rate on that job and the next one or two.
🤖 Generated with Claude Code