Large cache not restored
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hello!
I'm having issues with restoring a cache of approximately 2GB, created by the same branch on a pull request.
At the first run I'm able to create correctly the cache (according to the output of the action):

https://github.com/dariosortino/testci_multicore/actions/runs/4697852048/jobs/8329413441
After a push on the same branch (consequently having a re-run of the workflow), the cache can't be restored:

https://github.com/dariosortino/testci_multicore/actions/runs/4697956348/jobs/8329643936
And I can't even save again the cache since it's already there:

Since the cache is created by the branch itself, it should not be a visibility issue.
In fact, I also made some trials by caching a small test file, and everything works as expected (I can restore it correctly).
That's why I'm suspecting that it's a size issue at this point.
cc @RiccardoGrieco
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the cache logs in the two linked GitHub Actions workflow runs, then reproduce the behavior with the approximately 2GB cache and the small test file. Done means a cache created on a branch can be restored on a later run, without a failed restore or an inability to save because the cache already exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100