-
-
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
could not import internal/cpu (-: could not load export data: cannot import "internal/cpu" (unknown iexport format version 1), export data is newer version - update tool) #893
Comments
Hi, thank you for report. Is it only for go1.14? Probably we should rebuild golangci-lint with go1.14 after the release, but I'm not sure that it will help. |
I was able to reproduce with Go 1.14.x and latest cc @jirfag |
Be careful, if you update to a more recent version of golangci-lint/pkg/golinters/govet.go Lines 80 to 83 in cb2f8ba
This condition matches for some analyzers, such as printf , because they changed it in x/tools "recently".If you configure the key linters-settings.govet.settings.printf in the config file, it will throw an error about unknown/invalid key.
This error occurred for me, because I was not able to run golangci-lint with Go 1.14. |
@pierrre Thanks for the follow up. We actually haven't updated |
I can't do it, because I'm not using it in a project. But I'm sure that the |
The golangci-lint linter runs into issue [0] when linting airshipctl with go1.14. This uplifts the linter to a version in which the issue is fixed. [0] golangci/golangci-lint#893 Change-Id: I50d3c4ab2533c1d14d01effed21906f0ef79aafc
after e4d31d, the linter does nto finish its job and complains with "WARN [runner] Can't run linter goanalysis_metalinter" and "export data is newer version - update tool". This is described here golangci/golangci-lint#893. The solution is to use newer golangci-lint, which is done here. Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
after e4d31d, the linter does nto finish its job and complains with "WARN [runner] Can't run linter goanalysis_metalinter" and "export data is newer version - update tool". This is described here golangci/golangci-lint#893. The solution is to use newer golangci-lint, which is done here. Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
* chore(*) bump gloangci-lint version after e4d31d, the linter does not finish its job and complains with "WARN [runner] Can't run linter goanalysis_metalinter" and "export data is newer version - update tool". This is described here golangci/golangci-lint#893. The solution is to use newer golangci-lint, which is done here. * fix(kuma-cp) remove deprecated functin call Go 1.14 deprecates BuildNameToCertificate as described here golang/go#37626 Fixing the linter exposes this issue and it's fixed here. * chore(*) cleanup dependencies `go mod tidy` * chore(*) add more `-mod=mod` where needed * fix(kuma-cp) fix failing linter after rebase to new k8s Also Move the namespace creation to BeforeSuite section in k8s store testing. * chore(*) add tidy target for go mod maintenance * chore(*) commit the result of the tidy * fix(*) pushd/popd are not always available in a Makefile Signed-off-by: Nikolay Nikolaev <nikolay.nikolaev@konghq.com>
Thank you for creating the issue!
Please include the following information:
Version of golangci-lint
Config file
Go environment
Verbose output of running
There are two warnings in the output, the first is this issue, the second looks like #827.
The issue is present for versions 1.21.0, 1.20.1 and 1.20.0. It is not present for version 1.19.1.
The text was updated successfully, but these errors were encountered: