-
Notifications
You must be signed in to change notification settings - Fork 19
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
Permissions denied to delete files #13
Comments
@LucilleH are you familiar already with how to edit the permissions for this action? If not, I can look into it. |
I also ran into that issue, and can provide a "live example" for debugging. Perhaps useful to you. In that example, that pipeline step is fine and finishes, like the OP observed as well. However, that run was a couple days ago, and by now the install pipeline step itself doesn't finish successfully anymore. Not sure if that's related to the EDIT: Nope, second issue is unrelated to first one. Removing |
@alexpovel thanks for reporting your experience. I pulled out the second bug into its own issue #15. We are looking into it. |
From https://github.com/alexpovel/ancv/actions/runs/6047793118/job/16411917582#step:3:173
These errors seem to be from the nix installer trying to clean up itself. |
### Description macOS caching is broken. This PR fixes it. This is related to `gtar` not having `sudo` permission, but `/nix/store` requires sudo. There are many many related issues out there. eg. actions/cache#749 I also switched to using DeterminateSystems nix installer. However, I noticed that even though cache is successfully restored in the latest round of CICD, we are still fetching the binaries from remote? (at least based on the log lines) Why is that? I suspect that I'm missing some sqlite data in the cached files. cc @savil @gcurtis if any of you have insights into this. EDIT: SOLVED. Added xdg paths in the cache and it reduces the time by half. 🎉 🎉 🎉 closes #13
devbox-install-action
seems to be missing permissions to clean up it's own files.This doesn't seem to affect the pipeline outcome, but it generates a lot of logs.
I call the action as follows:
Logs
The text was updated successfully, but these errors were encountered: