Open dariosortino opened 1 year ago
This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days.
Waiting for news
We are also waiting for news. Our cache is approximately 2.3 GB, and constantly depends on infinity. We hoped that the action/cache@3 version would solve the problem, but alas, the problem is still relevant. Also, the timeout, which was written in 10 minutes by default, was not implemented. Moreover, after clicking “cancel” the ci work, a stack trace appears as if the cache has been completely downloaded and it seems that the problem is at the data unpacking level.
Total: actions/cache@3 macos - 12 cache size ~ 2.3 gb The timeout does not work and the job runs endlessly
And now I tried again, indeed - the cache itself downloads in about a minute and a half, and then the command /usr/local/bin/gtar -xf /Users/runner/work/_temp/4798228d-a051-4660-bb3a-88093636a9c3/ is launched cache.tzst -P -C /Users/runner/work/InsalesMobile/InsalesMobile --delay-directory-restore --use-compress-program unzstd and hangs on it indefinitely
This issue is stale because it has been open for 200 days with no activity. Leave a comment to avoid closing this issue in 5 days.
𝑯𝒆𝒍𝒍𝒐
Hi, any news on this? We're also having a similar problem. We have a 1.7gb cache that, sometimes, hangs in there for minutes for both compressing or decompressing. It logs the following command:
/usr/bin/tar -xf /runner/_work/_temp/afa3a5fc-6b2b-42a5-848b-f19bc9ab3c1d/cache.tzst -P -C /runner/_work/REPO --use-compress-program unzstd
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