Skip to content
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

Large cache not restored #1151

Open
dariosortino opened this issue Apr 14, 2023 · 7 comments
Open

Large cache not restored #1151

dariosortino opened this issue Apr 14, 2023 · 7 comments

Comments

@dariosortino
Copy link

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):
image
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:
image
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:
image

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

Copy link

github-actions bot commented Nov 1, 2023

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.

@github-actions github-actions bot added the stale label Nov 1, 2023
@dariosortino
Copy link
Author

Waiting for news

@github-actions github-actions bot removed the stale label Nov 2, 2023
@JerakRus
Copy link

JerakRus commented Dec 14, 2023

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.

Снимок экрана 2023-12-14 в 18 20 37
Снимок экрана 2023-12-14 в 18 21 08

Total:
actions/cache@3
macos - 12
cache size ~ 2.3 gb
The timeout does not work and the job runs endlessly

@JerakRus
Copy link

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

Copy link

github-actions bot commented Jul 2, 2024

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.

@github-actions github-actions bot added the stale label Jul 2, 2024
@Bonita666
Copy link

𝑯𝒆𝒍𝒍𝒐

@ericksm3
Copy link

ericksm3 commented Jul 2, 2024

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

@github-actions github-actions bot removed the stale label Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants