We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug The post step is marked as failed when attempting to upload a cache that already exists.
It looks like the cache API is now returning a different error message when the cache already exists. It used to say:
Cache already exists: Error: reserveCache failed: Cache already exists. Scope: [...], Key: [...], Version: [...]
Now it says:
Error: Unexpected error: ReserveCacheError: Unable to reserve cache with key [...], another job may be creating this cache.
The LayerCache searches for "Cache already exists" in error messages to ignore that case, but the new message doesn't match that.
To Reproduce
Expected behavior Action to detect the new Unable to reserve cache and treat it as non-fatal.
Unable to reserve cache
Debug logs https://github.com/satackey/action-docker-layer-caching/runs/1507974881
Runner Environment (please complete the following information):
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Describe the bug
The post step is marked as failed when attempting to upload a cache that already exists.
It looks like the cache API is now returning a different error message when the cache already exists. It used to say:
Now it says:
The LayerCache searches for "Cache already exists" in error messages to ignore that case, but the new message doesn't match that.
To Reproduce
Expected behavior
Action to detect the new
Unable to reserve cache
and treat it as non-fatal.Debug logs
https://github.com/satackey/action-docker-layer-caching/runs/1507974881
Runner Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: