-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
"File exists" errors when un-taring golangci-lint on upgrading to setup-go@v4 from setup-go@v3 #807
"File exists" errors when un-taring golangci-lint on upgrading to setup-go@v4 from setup-go@v3 #807
Comments
@bombsimon yes, I had come across all the above mentioned issues before. We are already running unit tests after golangci-lint alraedy as mentioned in #23, which did not seem to help us much to mitigate the problem. This issue is raised because disabling cache is workaround, not a fix to this problem. |
Disabling the cache during the `setup-go` step was probably done to avoid errors from the `golangci-lint` step golangci/golangci-lint-action#807, golangci/golangci-lint-action#244), but the `setup-go` step isn't actually needed before running `golangci-lint`.
Every time a job is posted, I received false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I received false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 * fixed code coverage on all sub packages Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I received false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 * fixed code coverage on all sub packages Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 * added unit tests to internal package Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 * added unit tests to internal package Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 * ci: fixed code coverage on all sub packages Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 * ci: fixed code coverage on all sub packages Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Every time a job is posted, I receive false alarm failure notifications because of some cache conflict during the linting job. Reference: golangci/golangci-lint-action#807 Signed-off-by: Frederic BIDON <fredbi@yahoo.com>
Just ran into this error - it would be great to have a fix that enables good performance (which golangci-lint talks about in main README) by enabling caching without also having 16K lines of logs with file-exists errors. |
Welcome
Description of the problem
Error Snippet:
The issue can be resolved on setting cache: false with setup-golang:
Version of golangci-lint
v3
Version of the GitHub Action
Latest
Workflow file
Go version
v4
Code example or link to a public repository
https://github.com/RamenDR/ramen/blob/main/.github/workflows/ci.yaml
The text was updated successfully, but these errors were encountered: