Repository navigation
GitHub warns about new cache size limit #301
Description
Activity
I received the same mail and wondered where it came from - didn't realize that PythonQt uses caching for the ccache.
We should probably reduce the maximum cache size forhendrikmuhs/ccache-action, which is by default set to 500 MB, maybe something like 200MB. This would of course reduce the effectiveness of the cache, but hopefully not that much.- added 2 commits that reference this issue
on Sep 18, 2025 Hm, that doesn't really help. The builds are slower, and while the caches are smaller, their number increases with the number of branches, so the size limit is reached anyway.
I will make a few more tests.- added 7 commits that reference this issue
on Sep 19, 2025 I added a workflow that is supposed to delete caches for deleted or merged PRs, but it doesn't work due to permission problems. The workflow is basically taken straight from GH Actions help.
I also found elsewhere that this doesn't work in forks (I have seen similar behavior in other workflows), so I merged the changes in the hope that it will work after the merge. It didn't. I also added a setting to delete unused references from the caches, so now it takes a little longer until the caches reach the limit, but the problem is still unsolved.I wouldn't care much about GH deleting old caches in this repo automatically that exceed the limit (which it does), except that this is done apparently across repos, and I'm using caches in a number of other (Python) repos. I don't know what the algorithm for cache deletion is, but I wouldn't like to randomly lose caches in other repos.
@hmeine - I haven't seen the warnings for a while now. Setting
evict-old-filesseems to have helped - currently the used cache in PythonQt is about 2.5 GB.
I couldn't get the workflow to delete caches to work, but old caches are removed anyway after some time, soI'll probably just removeI removed that workflow again. It could still be that the problem reappears with many active PRs, but for now I will ignore this issue (and close it if the problem does not reappear after a couple of months).
I received an e-mail that looked too much like phishing at first, but turned out to be a legitimate warning from GitHub that some unnamed repo has exceeded the newly introduced cache size limit of 10G.
Some more research showed that the only repo I have access to that makes significant use of the cache is this one, and without adding up all the numbers it does look plausible that it exceeds 10 GiB (not by much, I guess):