-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls/internal/regtest/misc: TestRunGovulncheckError2 failures #57032
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
Comments
Found new dashboard test flakes for:
2022-12-01 19:51 netbsd-amd64-9_3 tools@e79e423f go@9f443332 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2022-12-01 19:51 linux-386 tools@e79e423f go@8fd2875c x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2022-12-01 19:51 openbsd-386-70 tools@e79e423f go@9f443332 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2022-12-01 21:10 linux-386-bullseye tools@0379b73a go@c71d3a0f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:10 linux-amd64-nocgo tools@0379b73a go@c71d3a0f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:10 linux-arm64-aws tools@0379b73a go@c71d3a0f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2022-12-01 21:10 netbsd-amd64-9_3 tools@0379b73a go@9f443332 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2022-12-01 21:30 linux-amd64-longtest tools@d54e12bf go@c71d3a0f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2022-12-01 21:30 netbsd-amd64-9_3 tools@d54e12bf go@e727f419 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
(attn @hyangah) |
Change https://go.dev/cl/454638 mentions this issue: |
Found new dashboard test flakes for:
2022-12-01 21:30 windows-arm64-10 tools@d54e12bf go@0e8b6056 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Skipping while investigating a better option to test error handling behavior. Updates golang/go#57032 Change-Id: Ifa7924a013ed092ac6acfc85f06aff48b2035721 Reviewed-on: https://go-review.googlesource.com/c/tools/+/454638 Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> gopls-CI: kokoro <noreply+kokoro@google.com> Reviewed-by: Robert Findley <rfindley@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Hyang-Ah Hana Kim <hyangah@gmail.com>
Found new dashboard test flakes for:
2022-12-01 21:30 linux-amd64-race tools@d54e12bf go@6a70292d x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Change https://go.dev/cl/454775 mentions this issue: |
Found new dashboard test flakes for:
2022-12-01 19:51 linux-amd64-alpine tools@e79e423f go@86963b45 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 19:51 linux-amd64-alpine tools@e79e423f go@8ed74ee3 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 19:51 linux-amd64-longtest tools@e79e423f go@c71d3a0f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 19:51 linux-amd64-longtest-race tools@e79e423f go@c71d3a0f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 19:51 linux-amd64-longtest-race tools@e79e423f go@8ed74ee3 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 19:51 linux-ppc64le-buildlet tools@e79e423f go@8ed74ee3 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:10 linux-amd64-clang tools@0379b73a go@e727f419 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:10 linux-ppc64le-buildlet tools@0379b73a go@e727f419 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:10 netbsd-386-9_3 tools@0379b73a go@e727f419 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:30 freebsd-arm64-dmgk tools@d54e12bf go@9f443332 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:30 linux-amd64-longtest-race tools@d54e12bf go@0e8b6056 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Change https://go.dev/cl/456636 mentions this issue: |
…vulncheckError2 Changes CompletedProgress to take an optional WorkState which is filled when the expectation is met (i.e. completed progress) Fixes golang/go#57032 Change-Id: Ie876d4d5a739e31b758b5affa2e9d6e4fb772dd5 Reviewed-on: https://go-review.googlesource.com/c/tools/+/454775 Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Hyang-Ah Hana Kim <hyangah@gmail.com> Reviewed-by: Robert Findley <rfindley@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> Reviewed-on: https://go-review.googlesource.com/c/tools/+/456636
Found new dashboard test flakes for:
2022-12-01 21:30 freebsd-arm64-dmgk tools@d54e12bf go@6a70292d x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:30 linux-amd64-longtest tools@d54e12bf go@6a70292d x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:30 linux-amd64-longtest-race tools@d54e12bf go@6a70292d x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2022-12-01 21:10 linux-amd64-longtest-race tools@0379b73a go@c71d3a0f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
2022-12-01 21:10 linux-ppc64le-buildlet tools@0379b73a go@c71d3a0f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2023-02-22 15:03 windows-amd64-race tools@e85b5336 go@7b398b1f x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2023-02-25 00:08 windows-amd64-race tools@f98fce20 go@ac556f35 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Found new dashboard test flakes for:
2023-02-27 20:01 windows-amd64-race tools@b0fcf2a0 go@ef793801 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Reoccurrence is #58714 |
Found new dashboard test flakes for:
2023-09-13 21:17 linux-s390x-ibm tools@715a4527 go@de4ead81 x/tools/gopls/internal/regtest/misc.TestRunGovulncheckError2 (log)
|
Looks like this was caused by two goroutines racing
And the test was checking whether last progress report contains explanation on the failure. Merging two streams (STDOUT/STDERR) into one progress report output stream is tricky. Especially, the info sent to STDOUT needs to be post-processed so it will add more delays. I think it would've been much simpler for govulncheck API users if the preamble and progress reports were out of the JSON streams |
Change https://go.dev/cl/528361 mentions this issue: |
Govulncheck scan API rarely outputs anything through STDERR. Messages shown in govulncheck scan API's stderr indicate real problems and it's better to show at the end when the scan fails. Buffer STDERR messages and sent them only when the command has failed and the goroutine that post-processes STDOUT stream has terminated. That will eliminate race between progress reports produced from STDERR and from STDOUT. Updates golang/go#57032 Change-Id: Ibd73668b11c07b83ea3aee55a43d6b8072c80870 Reviewed-on: https://go-review.googlesource.com/c/tools/+/528361 Reviewed-by: Alan Donovan <adonovan@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com>
@hyangah can this be closed? |
We could skip emitting Config and Progress messages from the I am curious, in what sense would it be easier to use the API if the Config and Progress are not emitted? |
We think this is fixed. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: