-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls/internal/regtest/modfile: TestSumUpdateFixesDiagnostics failures with "Unmet: empty diagnostics" #51352
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
One notable thing about this builder is that its connection to I wonder if |
This does not appear to be specific to the
2022-04-03T23:48:16-153e30b-ba6df85/windows-arm64-11 |
|
Change https://go.dev/cl/398699 mentions this issue: |
…agnostics This test is somewhat noisy on the builders. I'd like to skip it until someone can look into it in more depth. For golang/go#51352. Change-Id: I2aa5c9c279807b57872324d84c1bb585cdf34d06 Reviewed-on: https://go-review.googlesource.com/c/tools/+/398699 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> Reviewed-by: Robert Findley <rfindley@google.com>
Change https://go.dev/cl/423974 mentions this issue: |
Metadata reloading has been significantly refactored recently. Unskip this test to see if it still flakes. For golang/go#51352 For golang/go#53878 Change-Id: I9f2ae1835bbace1b5095c2d45db082c4e709437b Reviewed-on: https://go-review.googlesource.com/c/tools/+/423974 Run-TryBot: Robert Findley <rfindley@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> gopls-CI: kokoro <noreply+kokoro@google.com> Reviewed-by: Peter Weinberger <pjw@google.com>
Looks like this is no longer flaking. Closing. |
greplogs --dashboard -md -l -e 'FAIL: TestSumUpdateFixesDiagnostics .*(?:\n .*)*Unmet: empty diagnostics' --since=2022-02-02
2022-02-23T19:46:34-258e473-e534907/linux-amd64-wsl
2022-02-17T17:37:50-a317113-eaf0405/linux-amd64-wsl
2022-02-16T18:05:27-11109f6-a289e9c/linux-amd64-wsl
CC @findleyr @mengzhuo
The text was updated successfully, but these errors were encountered: