-
Notifications
You must be signed in to change notification settings - Fork 743
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
/usr/bin/tar: ../../../../home: Cannot mkdir: Permission denied #315
Comments
Hello @jvermillard. Thank you for your report. We'll investigate the issue. |
Hello @jvermillard. Could you please provide link to the public repository. I've tried to reproduce the issue but everything works as expected. |
ok let me create an example |
I tried with a brand new repository and I don't have the issue 🤔 So the context is I moved a provjet from a slef-hosted runner to the managed runners and I got this issue. Do you think this would have caused the cache issue ? |
Hello @jvermillard. Thank you for your response. I think the faster way will be to change fileHash by editing pom.xml. Another solution is to wait a week with no builds while the cache will be cleared. |
Hello @jvermillard. Do you have any updates ? |
even if i change the pom.xml I still have:
|
Hello @jvermillard. Th setup-java action has restore-keys that is why it restores previous action after changing pom.xml. I think it was an internal issue with GitHub Actions itself, that is why It can be reproduced for different repository with new cache it works as expected. For now I'm going to close the issue. If you have any concerns feel free to ping us. |
Hello @jvermillard, did you ever find a solution to the above? We are facing the exact same issue (albeit with actions/cache). We are creating the cache on self-hosted runner, but when we then try to access/restore that cache on a github hosted runner, it fails with the error below. However, we are always successful restoring that same cache at any time on the self-hosted runner.
Any feedback you have is greatly appreciated! |
@my3sons I don't really remeber, I think I deleted the cache and it did the trick |
Description:
Task version:
Specify the task version
Platform:
Runner type:
Repro steps:
use this workflow:
Expected behavior:
Not failing at mkdir step
Actual behavior:
Early failure of the action
The text was updated successfully, but these errors were encountered: