You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes, I understand that the GitHub action repository is not the repository of golangci-lint itself.
Yes, I've searched similar issues on GitHub and didn't find any.
Yes, I've included all information below (version, config, etc).
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
first run
second run
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.
production log from GH actions
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.
same command in local cli
Version of golangci-lint
latest - 1.52.2
Version of the GitHub Action
3
Workflow file
setup-go uses actions/setup-go@v3 along with few other configuration to include the private vendors, install go dependencies and caching those dependecies.
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: