Can't run linter goanalysis_metalinter: rowserrcheck: failed prerequisites #1011
Closed
3 tasks done
Comments
|
I'm having a similar issue. Randomly CI build fails like this: https://github.com/umputun/remark42/runs/568704660?check_suite_focus=true#step:7:43 go 1.14, golangci-lint 1.24 |
|
I am also having this issue, the linter throws these prerequisite errors. |
|
This is very cryptic and flaky bug :( Can you confirm that |
yes |
|
Yup, using 1.23.8 with Go 1.14 seems to be fine. Its only when I upgrade to 1.24 does the bug reproduce consistently. |
ernado
added a commit
that referenced
this issue
Apr 22, 2020
|
Please try |
|
I have switched to 1.25.0. So far so good, but had just a few builds on GitHub actions |
jirfag
added a commit
that referenced
this issue
May 3, 2020
The primary improvement is in early clearing of
analyzed package's TypeInfo, facts, etc for
whole program analyzers (`unused`). Clear it when it
becomes unused and GC collects them early. Initially this
clearing was performed for all analyzers except `unused`.
Update staticcheck from v0.0.1-2019.2.3 to v0.0.1-2020.1.4
Also in this commit:
* speed up loading packages from export data (2.5s -> 2.1s for std)
by not using mutex for export data since it was allowed in
x/tools#07722704da13
* make an order of execution of linters stable
* update renameio and robustio
* use robustio in caching
Relates: #987, #994, #995, #1011
jirfag
added a commit
that referenced
this issue
May 3, 2020
The primary improvement is in early clearing of
analyzed package's TypeInfo, facts, etc for
whole program analyzers (`unused`). Clear it when it
becomes unused and GC collects them early. Initially this
clearing was performed for all analyzers except `unused`.
Update staticcheck from v0.0.1-2019.2.3 to v0.0.1-2020.1.4
Also in this commit:
* speed up loading packages from export data (2.5s -> 2.1s for std)
by not using mutex for export data since it was allowed in
x/tools#07722704da13
* make an order of execution of linters stable
* update renameio and robustio
* use robustio in caching
Relates: #987, #994, #995, #1011
jirfag
added a commit
that referenced
this issue
May 3, 2020
The primary improvement is in early clearing of
analyzed package's TypeInfo, facts, etc for
whole program analyzers (`unused`). Clear it when it
becomes unused and GC collects them early. Initially this
clearing was performed for all analyzers except `unused`.
Update staticcheck from v0.0.1-2019.2.3 to v0.0.1-2020.1.4
Also in this commit:
* speed up loading packages from export data (2.5s -> 2.1s for std)
by not using mutex for export data since it was allowed in
x/tools#07722704da13
* make an order of execution of linters stable
* update renameio and robustio
* use robustio in caching
Relates: #987, #994, #995, #1011
jirfag
added a commit
that referenced
this issue
May 5, 2020
The primary improvement is in early clearing of
analyzed package's TypeInfo, facts, etc for
whole program analyzers (`unused`). Clear it when it
becomes unused and GC collects them early. Initially this
clearing was performed for all analyzers except `unused`.
Update staticcheck from v0.0.1-2019.2.3 to v0.0.1-2020.1.4
Also in this commit:
* speed up loading packages from export data (2.5s -> 2.1s for std)
by not using mutex for export data since it was allowed in
x/tools#07722704da13
* make an order of execution of linters stable
* update renameio and robustio
* use robustio in caching
Relates: #987, #994, #995, #1011
brimstone
pushed a commit
to storj/ci
that referenced
this issue
Jun 3, 2020
https: //github.com/golangci/golangci-lint/issues/1011 Change-Id: I9156d152401cb1f9074a63c1a7859c72854fbd6c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thank you for creating the issue!
Please include the following information:
Version of golangci-lint
Config file
Go environment
Verbose output of running
Here is the log on GitHub:
https://github.com/logur/logur/runs/558348594?check_suite_focus=true
Disabling
rowserrcheckis not enough:https://github.com/logur/logur/runs/558551895?check_suite_focus=true
Cannot reproduce it locally though.
The text was updated successfully, but these errors were encountered: