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
Caching of the linting data causing timeout. #730
Labels
Comments
fho
added a commit
to simplesurance/baur
that referenced
this issue
May 17, 2023
Enabled cache causes golangci-lint to timeout. This might be the issue described in: golangci/golangci-lint-action#730
2 tasks
Hello, The caching process has been improved. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Welcome
Description of the problem
The issue at hand is related to the linting process, when the lint job is executed more than once with netrox/act on a local machine or in a GitHub Action, it gets timeout and even with timeout it takes a lot of time. Two example of run are as follows
As per my understanding this problem arises when the golangci-lint tool, caches its data during the first run and reuses it on the second run. This causes the available memory to be reduced to less than 100mb, leading to a timeout error during the linting process. The error message indicates that there's not enough memory available to complete the process.
This problem has been identified by examining the logs from the production environment.
One workaround to solve this issue is to add a timeout to the linting process, but this can significantly increase the time it takes to complete the job. This is not an ideal solution, as it can slow down the development process and cause delays. Given this delay is much higher than the cli tool, it's becomes really slower in comparison.
Version of golangci-lint
latest - 1.52.2
Version of the GitHub Action
3
Workflow file
Go version
1.18
Code example or link to a public repository
Private repo code cant be shared.
// add your code here
The text was updated successfully, but these errors were encountered: