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

CircleCI is failing on test_backend, because /cache/docker.tar is not restored #1686

Closed
jwhitlock opened this issue Mar 24, 2022 · 1 comment · Fixed by #1690
Closed

CircleCI is failing on test_backend, because /cache/docker.tar is not restored #1686

jwhitlock opened this issue Mar 24, 2022 · 1 comment · Fixed by #1690

Comments

@jwhitlock
Copy link
Member

After merging PR #1624, builds are failing on the test_backend job, on the "Restore Docker image" step:

docker load --input /cache/docker.tar
open /cache/docker.tar: no such file or directory
Exited with code exit status 1

Working backwards, the step "Restoring cache" is failing to load the file:

Found a cache from build 9011 at v1-backend-build-main
Size: 508 MiB
Cached paths:
  * /cache/docker.tar

Downloading cache archive...
Unarchiving cache...
Skipping writing "cache/docker.tar" - open /cache/docker.tar: no such file or directory

This is created by the build_backend job, in the "Saving cache" step:

Creating cache archive...
Uploading cache archive...
Stored Cache to v1-backend-build-main-1648139534
  * /cache/docker.tar
Total size uploaded: 508 MiB

The CircleCI cache documentation suggests that the cache has size limits:

We recommend keeping cache sizes under 500MB. This is our upper limit for corruption checks. Above this limit, check times would be excessively long. You can view the cache size from the CircleCI Jobs page within the restore_cache step. Larger cache sizes are allowed, but may cause problems due to a higher chance of decompression issues and corruption during download. To keep cache sizes down, consider splitting them into multiple distinct caches.

It is possible that we're seeing a transitory issue.

@jwhitlock
Copy link
Member Author

I've been working on this issue, but didn't file it first. Some attempts:

I'll probably return to this in the morning.

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

Successfully merging a pull request may close this issue.

1 participant