-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/go/analysis/unitchecker: TestVetStdlib failures #60058
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:
2023-05-08 19:51 linux-arm64-longtest tools@8f7fb01d go@4576184b x/tools/go/analysis/unitchecker.TestVetStdlib (log)
|
Found new dashboard test flakes for:
2023-05-08 19:51 linux-386-longtest tools@8f7fb01d go@4576184b x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2023-05-08 19:51 linux-amd64-longtest tools@8f7fb01d go@4576184b x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2023-05-08 19:51 linux-amd64-longtest-race tools@8f7fb01d go@4576184b x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2023-05-08 19:51 windows-amd64-longtest tools@8f7fb01d go@4576184b x/tools/go/analysis/unitchecker.TestVetStdlib (log)
|
Found new dashboard test flakes for:
2023-05-08 19:51 darwin-amd64-longtest tools@8f7fb01d go@4576184b x/tools/go/analysis/unitchecker.TestVetStdlib (log)
|
This was fixed on master thanks to Russ's https://go.dev/cl/493598. |
@gopherbot please backport to 1.20. |
Backport issue(s) opened: #60927 (for 1.20). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://go.dev/wiki/MinorReleases. |
Change https://go.dev/cl/504977 mentions this issue: |
The unused analyzer handles dot imports now, so a few tests have picked up vet errors. This CL errors like: context/x_test.go:524:47: result of context.WithValue call not used This is a manual cherry-pick of CL 493598. Updates #60058 Fixes #60927 Change-Id: I92906ef7967e14a85fa974e6307fd689e3ff3dba Reviewed-on: https://go-review.googlesource.com/c/go/+/504977 Auto-Submit: Heschi Kreinick <heschi@google.com> TryBot-Bypass: Heschi Kreinick <heschi@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Alan Donovan <adonovan@google.com>
Found new dashboard test flakes for:
2024-01-05 17:34 linux-386-longtest tools@ba8672b5 go@c0693f64 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2024-01-05 17:34 linux-386-longtest tools@ba8672b5 go@8db13108 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2024-01-05 17:34 linux-amd64-longtest tools@ba8672b5 go@c0693f64 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2024-01-05 17:34 linux-amd64-longtest tools@ba8672b5 go@8db13108 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2024-01-05 17:34 linux-arm64-longtest tools@ba8672b5 go@c0693f64 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2024-01-05 17:34 linux-arm64-longtest tools@ba8672b5 go@8db13108 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
|
Found new dashboard test flakes for:
2024-01-05 17:34 linux-amd64-longtest-race tools@ba8672b5 go@c0693f64 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2024-01-05 17:34 linux-amd64-longtest-race tools@ba8672b5 go@8db13108 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2024-01-05 17:34 windows-amd64-longtest tools@ba8672b5 go@c0693f64 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
2024-01-05 17:34 windows-amd64-longtest tools@ba8672b5 go@8db13108 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
|
Found new dashboard test flakes for:
2024-01-05 17:34 darwin-amd64-longtest tools@ba8672b5 go@8db13108 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
|
Longtest builders are failing on 1.21 and 1.22 release branches (but not on tip and 1.20 release branch): https://ci.chromium.org/p/golang/g/x-tools-go1.21/console Since it's affecting first-class ports, it's blocking the monthly tagging workflow. Adding Soon label. Mailed CL 554755 to pull in the change made in CL 554196 into release-branch.go1.22. |
Change https://go.dev/cl/554756 mentions this issue: |
…nctions This will otherwise trigger an "unusedresult" vet check. For #64978. Fixes #65023. Fixes #60058. Change-Id: Ie19aded0f808d394f389452c3ff7f3edc1ed710d Reviewed-on: https://go-review.googlesource.com/c/go/+/554196 LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Bryan Mills <bcmills@google.com> (cherry picked from commit 8088b6d) Reviewed-on: https://go-review.googlesource.com/c/go/+/554756 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Alan Donovan <adonovan@google.com>
The instance reported 5 days ago is fixed by the CLs mentioned above; closing. |
Found new dashboard test flakes for:
2024-01-05 17:34 x_tools-gotip-darwin-amd64-longtest tools@ba8672b5 go@8db13108 x/tools/go/analysis/unitchecker.TestVetStdlib (log)
|
The report 1 hr ago (#60058 (comment)) is the same Go commit and x/tools commit as the earlier one (#60058 (comment)). The difference is it came from LUCI builders instead of old builders. |
Found new dashboard test flakes for:
2024-02-16 15:54 x_tools-gotip-darwin-amd64-longtest tools@0d171942 go@86a32d6d x/tools/go/analysis/unitchecker.TestVetStdlib [ABORT] (log)
|
This is almost certainly a dup of the hanging go command issue on darwin, #54461. |
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: