-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Lint passes unexpectedly when build fails #866
Labels
Comments
This was referenced Nov 23, 2019
3 tasks
rhcarvalho
added a commit
to rhcarvalho/sentry-go
that referenced
this issue
Dec 13, 2019
The current recommended installation steps use githubusercontent.com instead of goreleaser.com. There has been a reported issue in which the installer code differed between the two sites. golangci/golangci-lint#575 Additionally, pin to a specific tagged version of the install script to ensure reproducible installations of the tool. Use version 1.19.1. The latest two releases (1.21.0, 1.20.0) have a flaky bug (at least on macOS) that prevents the linter to run while still exiting with code 0 (success). ``` ~/s/sentry-go ❯❯❯ golangci-lint run WARN [runner] Can't run linter goanalysis_metalinter: assign: failed prerequisites: [email protected]/getsentry/sentry-go/echo ~/s/sentry-go ❯❯❯ golangci-lint run WARN [runner] Can't run linter goanalysis_metalinter: interfacer: failed prerequisites: [email protected]/getsentry/sentry-go/echo ``` See - golangci/golangci-lint#866 - golangci/golangci-lint#827
rhcarvalho
added a commit
to rhcarvalho/sentry-go
that referenced
this issue
Dec 13, 2019
The current recommended installation steps use githubusercontent.com instead of goreleaser.com. There has been a reported issue in which the installer code differed between the two sites. golangci/golangci-lint#575 Additionally, pin to a specific tagged version of the install script to ensure reproducible installations of the tool. Use version 1.19.1. The latest two releases (1.21.0, 1.20.0) have a flaky bug (at least on macOS) that prevents the linter to run while still exiting with code 0 (success). ``` ~/s/sentry-go ❯❯❯ golangci-lint run WARN [runner] Can't run linter goanalysis_metalinter: assign: failed prerequisites: [email protected]/getsentry/sentry-go/echo ~/s/sentry-go ❯❯❯ golangci-lint run WARN [runner] Can't run linter goanalysis_metalinter: interfacer: failed prerequisites: [email protected]/getsentry/sentry-go/echo ``` See - golangci/golangci-lint#866 - golangci/golangci-lint#827
rhcarvalho
added a commit
to getsentry/sentry-go
that referenced
this issue
Dec 13, 2019
The current recommended installation steps use githubusercontent.com instead of goreleaser.com. There has been a reported issue in which the installer code differed between the two sites. golangci/golangci-lint#575 Additionally, pin to a specific tagged version of the install script to ensure reproducible installations of the tool. Use version 1.19.1. The latest two releases (1.21.0, 1.20.0) have a flaky bug (at least on macOS) that prevents the linter to run while still exiting with code 0 (success). ``` ~/s/sentry-go ❯❯❯ golangci-lint run WARN [runner] Can't run linter goanalysis_metalinter: assign: failed prerequisites: [email protected]/getsentry/sentry-go/echo ~/s/sentry-go ❯❯❯ golangci-lint run WARN [runner] Can't run linter goanalysis_metalinter: interfacer: failed prerequisites: [email protected]/getsentry/sentry-go/echo ``` See - golangci/golangci-lint#866 - golangci/golangci-lint#827
This should error in latest versions, we've switched from warnings to errors in this place. |
I can confirm this is fixed, thanks
…On Tue, Feb 4, 2020 at 12:43 PM Aleksandr Razumov ***@***.***> wrote:
Closed #866 <#866>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#866?email_source=notifications&email_token=AAEYGXN3E2QN5X5OHSI7DDLRBHHNRA5CNFSM4JQ2RRP2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOWNCNX2Q#event-3007634410>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEYGXPE6S62ZQIRODS254LRBHHNRANCNFSM4JQ2RRPQ>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Thank you for creating the issue!
Please include the following information:
Version of golangci-lint
Config file
Go environment
$ go version && go env 1.13.4
Verbose output of running
Basically what is happening is we checked in a change to a test that is not run in CI, so all of our tests pass and the change gets merged. golangci-lint lints this file, but skips it because it doesn't build.
I would argue that it should fail if the build fails. This is especially important because it makes the entire lint process skips linting the entire code base because one random file was invalid. See this test, where I finally found what was going on and fixed the bad file, now we fail 50 lints because we haven't had it running for about a month: https://prow.istio.io/view/gcs/istio-prow/pr-logs/pull/istio_istio/19137/lint_istio/4192.
The text was updated successfully, but these errors were encountered: