-
Notifications
You must be signed in to change notification settings - Fork 391
gha - adapt cache saving to new actions/cache@v4 #12108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
It seems new cache API has changed a few things as we are hitting this issue with
I subscribed to upstream issue and we'll see. Restoring and saving cache seems to have become more complicated, especially when a new cache key will be necessary. As we are running multiple workflow in parallel, in case of new cache
Not a problem to have a working workflow but a lot of noise as Warning in log 😞 Let's see if they can improve this - I may find a workaround otherwise. |
|
This PR also try to fix Typst caching. The new cache API in github does not allow to save always the cache as before. It is now immutable and can't be updated. So this needs to be improved for more efficiency. Or we need to delete cache more regularly. I'll see later. |
`save-always` is deprecated, and now it needs to be a two step process: restore and save based on adaptation at r-lib/actions/setup-renv in r-lib/actions@108c7a6 gha - new cache does not allow overwrite and it does not deal with skipping existing cache. So it is a bit different that `save-always`. Cache will only be updated when renv.lock changes
with new cache we can't alway save the cache anymore without removing previous one. This means typst caching is way less efficient than designed initially. This change will allow to use the cache, but it will require manual update of the id to trigger a new caching
814da3a to
5654444
Compare
This reverts commit 210961e. Julia cache is required to speed up each job. However, the caching mechanism is still a problem as it will throw a warning for each other job than the one which managed to save with action v4 Saving a cache for each buckets would be too heavy in total storage (we are limited to 10Go).
|
quite verbose because of what is discussed at actions/cache#1541 We'll live with that until I managed to improve it |

save-alwaysis deprecated, and now it needs to be a two step process: restore and savebased on adaptation at r-lib/actions/setup-renv in r-lib/actions@108c7a6