| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Thanks @hugovk for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13, 3.14, 3.15. |
Sorry, something went wrong.
|
GH-153231 is a backport of this pull request to the 3.15 branch. |
Sorry, something went wrong.
|
GH-153232 is a backport of this pull request to the 3.14 branch. |
Sorry, something went wrong.
|
GH-153233 is a backport of this pull request to the 3.13 branch. |
Sorry, something went wrong.
|
This is working well. Just after this was merged, there were 53 caches with key:setup, three on main and the rest for PRs. 12 hours later, there's 29: the three main caches are being re-used, and the old per-PR caches are no longer needed and are dropping off the end. https://github.com/python/cpython/actions/caches?query=key%3Asetup |
Sorry, something went wrong.
…153231) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
…153232) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
…153233) Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>
| Back | FazBrowse Home | New Git URL |
Our GitHub Actions cache is always full:
https://github.com/python/cpython/actions/caches
Right now, PR caches use up 3.54 GB across 52 PRs:
They tend to get evicted after about a day due to the storage limit, and don't last the full 7-day limit.
But why are there so many caches for PRs?
Nearly all of this is pip caches from docs builds, and they're virtually identical.
There's also about Hypothesis cache of about 6 MB for the main branch. For Hypothesis, PRs usually use the main cache and don't need to write their own cache.
However, the docs workflow only runs for PRs, so main/3.* branches never get to save a cache. If they had, the vast majority would just use a cache from main and carry on. No need to save their own PR cache.
We can do this by letting this workflow run on main and 3.*, and also limit to only run if one of these files change: