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
Is your feature request related to a problem? Please describe.
When developing, my build is most of the time broken. I often want to identify all non-compiling packages. I can easily do this with go build for my main sources, but this does not work for test sources. I want an easy to use solution to find all my non-compiling tests.
Describe the solution you'd like
If I run golangci-lint run in a directory with several packages where tests can't compile, I want them to be printed to the console in the same way that linter errors are printed.
The functionality is already there: build errors are printed, but only the first error is printed and in a non-easy-to-use format. An example:
If I now run golangci-lint run, I get this output:
WARN [runner] Can't run linter goanalysis_metalinter: S1021: failed prerequisites: [([email protected]/torkelrogstad/build-tests/foo [github.com/torkelrogstad/build-tests/foo.test], [email protected]/torkelrogstad/build-tests/foo [github.com/torkelrogstad/build-tests/foo.test]): analysis skipped: errors in package: [/Users/torkel/dev/build-tests/foo/foo_test.go:9:6: Prin not declared by package fmt]]
WARN [runner] Can't run linter unused: buildir: analysis skipped: errors in package: [/Users/torkel/dev/build-tests/foo/foo_test.go:9:6: Prin not declared by package fmt]
ERRO Running error: buildir: analysis skipped: errors in package: [/Users/torkel/dev/build-tests/foo/foo_test.go:9:6: Prin not declared by package fmt]
It would be great to get this in the same format as linter errors.
The text was updated successfully, but these errors were encountered:
I have this same exact request. Currently, the errors are unbelievably unreadable (I have a lot on a rather large code base I'm not trying to integrate golangci-lint with). I know it's possible to limit the errors, but still this would be really nice
Is your feature request related to a problem? Please describe.
When developing, my build is most of the time broken. I often want to identify all non-compiling packages. I can easily do this with
go build
for my main sources, but this does not work for test sources. I want an easy to use solution to find all my non-compiling tests.Describe the solution you'd like
If I run
golangci-lint run
in a directory with several packages where tests can't compile, I want them to be printed to the console in the same way that linter errors are printed.The functionality is already there: build errors are printed, but only the first error is printed and in a non-easy-to-use format. An example:
I have a file
foo_test.go
If I now run
golangci-lint run
, I get this output:It would be great to get this in the same format as linter errors.
The text was updated successfully, but these errors were encountered: