-
Notifications
You must be signed in to change notification settings - Fork 56
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
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
- Run a workflow using this action to cache docker layers
- Push a change that will cause some new layers to build
- Run the workflow again with the same cache keys
- Observe the error message when already-cached files are uploaded
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):
- OS: ubuntu-18.04
- Action version: v0.0.10
msdrigg and tkrugg
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working