You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this on self-hosted github actions. I have two workflows running at the same time. The first one is able to save to the path (base), but when the second is trying to save the cache it gives the following error:
/usr/bin/mv: inter-device move failed: './node_modules' to '/home/runner/.github-cache/[hashed-cache-value]/node_modules'; unable to remove target: Directory not empty
As I see it, it is because the first job has already created the cache, so the second one fails because the cache/directory already exists. Would it make sense to ignore this kind of error, since this key/folder path should be unique? Or don't do the mv command if the directory already exists? Or add a with: parameter flag to ignore?
Thank you for your efforts with this action, it works quite well :)
The text was updated successfully, but these errors were encountered:
I'm using this on self-hosted github actions. I have two workflows running at the same time. The first one is able to save to the path (base), but when the second is trying to save the cache it gives the following error:
/usr/bin/mv: inter-device move failed: './node_modules' to '/home/runner/.github-cache/[hashed-cache-value]/node_modules'; unable to remove target: Directory not empty
As I see it, it is because the first job has already created the cache, so the second one fails because the cache/directory already exists. Would it make sense to ignore this kind of error, since this key/folder path should be unique? Or don't do the
mv
command if the directory already exists? Or add awith:
parameter flag to ignore?Thank you for your efforts with this action, it works quite well :)
The text was updated successfully, but these errors were encountered: