mirror of
https://github.com/nektos/act.git
synced 2026-04-26 09:25:54 +03:00
[GH-ISSUE #1787] Artifactcache: Failed to save cache entry 'already exist' #873
Labels
No labels
area/action
area/cli
area/docs
area/image
area/runner
area/workflow
backlog
confirmed/not-planned
kind/bug
kind/discussion
kind/external
kind/feature-request
kind/question
meta/duplicate
meta/invalid
meta/need-more-info
meta/resolved
meta/wontfix
meta/workaround
needs-work
pull-request
review/not-planned
size/M
size/XL
size/XXL
stale
stale-exempt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/act#873
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ChristianHersevoort on GitHub (May 5, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1787
Bug report info
Command used with act
Describe issue
Re-running act build fails because the cache entry already exists, however this works fine on github-actions.
Link to GitHub repository
No response
Workflow content
Relevant log output
Additional information
No response
@ChristopherHX commented on GitHub (May 5, 2023):
A cache entry is immutable (until it is evicted by cache size or passing 7days) act follows the behavior of GitHub Actions....
If you push a change then the cache key changes on GitHub.
However on act github.sha points to the same commit, you can provide a random value for
CACHE_KEY_JOB_EXECUTION_VARso the action uses a different key.--env CACHE_KEY_JOB_EXECUTION_VAR=somerandomvaluechangethistoupdatethecache@wolfogre commented on GitHub (May 6, 2023):
Since it works fine on GitHub Actions, I guess GitHub Actions may supports overwriting a cache entry.
I will try to do an experiment to verify, if the guess is true, I will update the logic in act.
Update: The guess is not true. "A cache today is immutable and cannot be updated." See https://github.com/actions/cache/blob/main/tips-and-workarounds.md#update-a-cache
@ChristopherHX commented on GitHub (May 6, 2023):
This is the response of the official cache backend, after the second attempt to save a cache with an existing key.
Other than improving the error message I don't think this is a bug.
Yes this feature has been requested on GitHub Actions, but it not there and I don't think act should do it differently
@github-actions[bot] commented on GitHub (Nov 4, 2023):
Issue is stale and will be closed in 14 days unless there is new activity