-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Issue with Saving Yarn Cache on Self-Hosted Runner #1113
Comments
Hello @marouanechoukri31, |
Hi @marouanechoukri31, This issue typically occurs in the following scenarios: Concurrent Jobs: Multiple jobs in the same workflow or different workflows are trying to create or reserve a cache with the same key simultaneously. Duplicate Cache Key: The cache key being used is not unique enough, causing conflicts when another job has already created a cache with the same key. To avoid this issue, you can try the following: 1. Ensure Unique Cache Keys: Modify the cache key to include more unique elements, such as a combination of job ID and timestamp. Here is an example of how you can modify the cache key to make it unique. This ensures that each job will have a unique cache key, reducing the likelihood of conflicts.
2. Implement actions/cache: Use the actions/cache action to handle caching directly.
|
Hi @marouanechoukri31, Just a gentle reminder regarding this issue, If you have any updates or need further assistance, Please let us know. |
1 similar comment
Hi @marouanechoukri31, Just a gentle reminder regarding this issue, If you have any updates or need further assistance, Please let us know. |
Hello @marouanechoukri31 |
Description:
A problem occurred while saving the yarn cache using a self-hosted runner. The process works correctly on the hosted runner.
Error :
Failed to save: Unable to reserve cache with key node-cache-macOS-yarn-33259bc05a9ff84ddf70121c6ada6b7886b9a8e9721b785469c879d852cc411e, another job may be creating this cache. More details: Cache already exists.
Code :
Action version:
Version 4
Platform:
Runner type:
Tools version:
Node version : 20.15.1
Yarn version : 1.22.22
The text was updated successfully, but these errors were encountered: