question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Saving cache is skipped

See original GitHub issue

Thank 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:open
  • Created 10 months ago
  • Comments:15 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
lukkacommented, Dec 1, 2022

@rcoup @cdcseacave i am taking my time to follow up on this, I won’t forget!

0reactions
lukkacommented, Dec 14, 2022

What do you mean by “cloud cache” — the GHA cache?

Yes, the GHA cache.

Workflows all running concurrently already clobber each other’s cache entries, that’s inevitable, and happens already if you push several commits requiring the (same) vcpkg rebuild. Caches are key-value stores though, so latest write “wins” — run-vcpkg/other actions don’t re-read the cache entries they’ve written earlier in a job, so doesn’t seem like a problem?

As far as I know the first wins, as the cache is immutable by design.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found