GHActions: Clean old stuff out of ccache - #14691
Open
TellowKrinkle wants to merge 4 commits into
Open
Conversation
TellowKrinkle
force-pushed
the
CacheClean
branch
from
July 13, 2026 03:09
83ca24b to
f80cb16
Compare
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
3 participants
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.
Description of Changes
Adds a CI step to clean stuff out of ccache caches if it hasn't been needed for a day.
(The clean runs after the build, so anything that was needed by the most recent build will be kept.)
Also fixes caches for AppImage debug builds, since I noticed they were previously shared with release builds, and turns off LTO for debug builds for faster cached builds.
Rationale behind Changes
We currently rely on our 100MB cache size limit to clear old stuff out of the ccache cache. This means all our ccache caches are near 100MB, which is kind of wasteful.
Suggested Testing Steps
Look at the size of the output cache for this PR
Did you use AI to help find, test, or implement this issue or feature?
No