Saving cache is skipped
See original GitHub issueThank you for trying to make this useful action, but it does not seem to be working. At the first build attempt that failed, it cached something (as much as it built to that point), but all the following pushes on that branch do not update the incomplete cache even if the build finishes successfully. See for ex: https://github.com/cdcseacave/openMVS/actions/runs/3513334392/jobs/5886034774
Am I using it wrong or I do not understand the purpose of this action?
PS: I also noticed that the buildtrees
and downloads
folder are cached, which seems to me like a big waste of space (actually the build fails with run out of space error if I do not remove these folders manually every time). Why do you cache these?
Issue Analytics
- State:
- Created 10 months ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
Saving cache stopped working ("Warning: skipping this step
Saving cache was working, but today I believe without changing anything we keep getting: Warning: skipping this step: disabled in ...
Read more >Skipping cache generation, cache already exists for key
The problem is the cache key you used is "dependencies", a plain string. This key never changes, so you will always use the...
Read more >Cache dependencies and build outputs in GitHub Actions
Skipping steps based on cache-hit Using the cache-hit output, subsequent steps (such as install or build) can be skipped when a cache hit...
Read more >Skipping cache extraction due to empty cache key - GitLab.org
Running yarn in an install of lint block works but like expected takes a long time which you want to save using the...
Read more >How to use the Gatsby Cache to skip subsequent external API ...
After successfully fetching data from the YouTube oEmbed API and asking Gatsy to create a node with the data, we save the current...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rcoup @cdcseacave i am taking my time to follow up on this, I won’t forget!
Yes, the GHA cache.
As far as I know the first wins, as the cache is immutable by design.