-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
cmd/go, x/tools: many tests are broken with go1.19.10 #60650
Comments
At least this should be pretty east to bisect. 😅 |
(Bisecting now.) |
Well then. Time to figure out what old bug we're tickling on the release branch. 😩 |
I suspect that the
But I don't know why that would be specific to 1.19. (My intuition is that it may be related to #29666, but we started using more precise |
This may also be related to the bug fixed in https://go.dev/cl/437298. I'll see if that backports cleanly, and if so whether it fixes the problem. |
I got it backported (with a couple of minor merge conflicts), but it doesn't seem to fix |
Change https://go.dev/cl/502175 mentions this issue: |
Change https://go.dev/cl/502195 mentions this issue: |
Change https://go.dev/cl/502196 mentions this issue: |
I have identified two backport CLs from #25842 that together appear to fix all of the broken |
Great, thank you, Bryan! |
The Config.Logf field enables debug logging in go/packages, which is exactly what we want when running a test in verbose mode to debug it. For golang/go#60650. Change-Id: I36b47e214860b5aec7c66042fc0ceb50c7062f1a Reviewed-on: https://go-review.googlesource.com/c/tools/+/502175 Reviewed-by: Michael Matloob <matloob@golang.org> TryBot-Bypass: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> gopls-CI: kokoro <noreply+kokoro@google.com>
At this point this is just waiting on the backport CLs to be merged by the release team. (I think @prattmic is on interrupts this week, but I'm not sure when in the process the release team usually does those merges.) |
Closed by merging c045822 to release-branch.go1.19. |
…o list -e -export go list -e -export puts errors running build actions on the load.Package corresponding to the failed action rather than exiting with a non zero exit code. Fixes #60710. Fixes #60650. Updates #25842. Change-Id: I1fea85cc5a0557f514fe9d4ed3b6a858376fdcde Reviewed-on: https://go-review.googlesource.com/c/go/+/437298 Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Michael Matloob <matloob@golang.org> Reviewed-on: https://go-review.googlesource.com/c/go/+/502195 TryBot-Bypass: Bryan Mills <bcmills@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com>
…n an error that includes the import path This refines the error output that was previously adjusted in CL 437298. Longer term, we should consider unraveling the call chains involving formatOutput to avoid passing so many parameters through so many different formatting functions. Updates #60710. Updates #60650. Updates #25842. Change-Id: I3b9d03bf5968902d8ccc4841ab4dbe114a2239e4 Reviewed-on: https://go-review.googlesource.com/c/go/+/451218 Reviewed-by: Bryan Mills <bcmills@google.com> Auto-Submit: Russ Cox <rsc@golang.org> Reviewed-by: Russ Cox <rsc@golang.org> Run-TryBot: Russ Cox <rsc@golang.org> Reviewed-by: Than McIntosh <thanm@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-on: https://go-review.googlesource.com/c/go/+/502196 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> TryBot-Bypass: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Michael Matloob <matloob@golang.org>
Many tests, for example
x/tools/go/packages
, are broken with Go 1.19.10.Here's an example trybot failure:
https://storage.googleapis.com/go-build-log/3ba9c890/linux-amd64_b61d03c6.log
And here's the failure for
go/packages
, which may be illustrative:Given the amount of tests that fail, it seems likely that this failure mode is user-facing.
CC @bcmills @matloob @rsc
The text was updated successfully, but these errors were encountered: