-
-
Notifications
You must be signed in to change notification settings - Fork 164
Golangci-lint exit with code 137 #552
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
Comments
We notice the same:
|
seems not to have this issue |
Hello, the context of this issue is not clear, can you provide more information (Go version, action version, etc.)? |
We also started getting this out of nowhere. Similar to @matzew it was resolved by upgrading from golangci-lint-action@v2 to v3 |
We have been facing the same issue, even with
|
I am still seeing this issue with the following:
The action is defined:
|
This issue seems related to the fact of using a golangci-lint version that does not support the Go version used in your CI.
|
I just updated my project to go 1.23, and I got this problem, which version do you recommend I use to solve it? Using version 1.60.3 it still gives the same error |
https://golangci-lint.run/welcome/faq/#which-go-versions-are-supported Basically, it's because you are using a golangci-lint binary that is not compiled with go1.23. The official binaries are compiled with go1.23 since v1.60.0. To check that: $ golangci-lint version
golangci-lint has version 1.61.0 built with go1.23.1 from a1d6c560 on 2024-09-09T17:44:42Z Also go1.23 should be installed inside your CI. |
I am using go 1.24 and golangci-lint 1.64.7(the latest) and could still get the error. Seems it needs lots of memory and OOM. So I add
|
Hey!
I'm running your GitHub lint action that worked great! but now somehow I started to get that
golangci-lint exit with code 137
error that was caused by Out Of Mem error.My conf
The text was updated successfully, but these errors were encountered: