Restoring error when go/pkg/mod exists in a self-hosted runner. #314
Assignees
Labels
bug
Something isn't working
Comments
daangn-rainn
changed the title
|
We will investigate this issue and come back to you. |
|
Hello @daangn-rainn! After the investigation, I come to you with the results. This is not actually a bug, but expected behavior, because as mentioned in the documentation, setup-go uses action/cache.
Hope it helps! |
|
Hello @daangn-rainn, did you have a chance to try one of the suggested solutions? Did it work for you? |
|
I hope the suggested steps were able to solve your problem. I'm closing this issue for now, but if you have any questions feel free to post them here or create a new one. |
6 tasks
ytimocin
added a commit
to radius-project/radius
that referenced
this issue
Jan 15, 2025
# Description Because the cache already exists on the GitHub runners we use, disabling cache in the setup-go steps of our CI/CD pipelines is expected solve the issue of seeing bunch of logs that say "**cannot open: file exists**". The official documentation of setup-go and the part that is relevant: https://github.com/actions/setup-go#caching-dependency-files-and-build-outputs. This points out that setup-go does caching for us. If the cache is already there, we will get all the logs in our workflows. There is no disadvantage of this approach, as far as I know, since the cache is already there. I actually ran into this [comment](actions/setup-go#403 (comment)) that says that disabling cache in setup-go step improved the speed of the said step. We can always update our workflows if we see any other disadvantages. Our runners: https://github.com/radius-project/radius/actions/runners. References: - actions/setup-go#403 - actions/setup-go#403 (comment) - actions/setup-go#314 (comment) ## Type of change - This pull request fixes a bug in Radius and has an approved issue (issue link required). Fixes: #7790 ## Contributor checklist Please verify that the PR meets the following requirements, where applicable: - [ ] An overview of proposed schema changes is included in a linked GitHub issue. - [ ] A design document PR is created in the [design-notes repository](https://github.com/radius-project/design-notes/), if new APIs are being introduced. - [ ] If applicable, design document has been reviewed and approved by Radius maintainers/approvers. - [ ] A PR for the [samples repository](https://github.com/radius-project/samples) is created, if existing samples are affected by the changes in this PR. - [ ] A PR for the [documentation repository](https://github.com/radius-project/docs) is created, if the changes in this PR affect the documentation or any user facing updates are made. - [ ] A PR for the [recipes repository](https://github.com/radius-project/recipes) is created, if existing recipes are affected by the changes in this PR. Signed-off-by: ytimocin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
When
~/go/pkg/moddir exists in a self-hosted runner, and I run setup-go, I can get the following messages in Run step.And also I can get the following messages in Post step.
But actually cache already exists, as Post step said. If I deleted that dir in action runner, setup-go can restore cache well and doesn't try to save cache.
Any help will be appreciated. It was too hard to find any resolutions.
Action version:
v3.5.0
Platform:
Amazon Linux 2
Runner type:
Self-hosted
Tools version:
1.18
Repro steps:
These are sample files.
Expected behavior:
A description of what you expected to happen.
Actual behavior:
A description of what is actually happening.
The text was updated successfully, but these errors were encountered: