-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/tools/gopls/internal/regtest/misc: TestRunVulncheckExpStd failures #56795
Comments
Found new dashboard test flakes for:
2022-11-09 17:16 netbsd-386-9_0 tools@502c6347 go@c3d444d0 x/tools/gopls/internal/regtest/misc.TestRunVulncheckExpStd (log)
|
(and can we set a timeout for vulncheck, so that we get a more meaningful failure here?) |
|
Looks like vulncheck only invokes a subprocess if we don't supply a Go version (but we do). It could have hung the call go go/packages.Load (which we run ad-hoc before calling vulncheck. I don't think we should investigate much before that netbsd bug is resolved, but it does seem like we could use more logging around the vulncheck invokation. @hyangah a good way to achieve that could be via intermediate progress updates while the command is running. |
Change https://go.dev/cl/452055 mentions this issue: |
Log before/after package loading and govulncheck.Source calls. All stderr output of `gopls vulncheck` command is forwarded to the client as LSP progress reports and visible to users. go/packages.Load can be traced further if GOPACKAGESDEBUG env var is set. Instrumentation in govulncheck.Source is still under discussion in upstream. For golang/go#56795 Change-Id: I8244930494aed17b319887bf96c2523f3215fa50 Reviewed-on: https://go-review.googlesource.com/c/tools/+/452055 Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Suzy Mueller <suzmue@golang.org> gopls-CI: kokoro <noreply+kokoro@google.com>
The test is renamed. Let's see if watchflakes find more info with new test names. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: