-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: livelock when computing module graph in a workspace with GOPROXY=off #53874
Comments
@gopherbot, please backport to Go 1.18 and 1.19 |
Backport issue(s) opened: #53875 (for 1.18), #53876 (for 1.19). 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/417594 mentions this issue: |
Change https://go.dev/cl/417656 mentions this issue: |
…cies with errors Fixes #53875. Updates #53874. Change-Id: I41ab15cb9b86b807a9d9ad21fe21fb7aa5fbb46f Reviewed-on: https://go-review.googlesource.com/c/go/+/417594 Run-TryBot: Bryan Mills <bcmills@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org> (cherry picked from commit a906d3d) Reviewed-on: https://go-review.googlesource.com/c/go/+/417656
Fixes golang#53874. Change-Id: I41ab15cb9b86b807a9d9ad21fe21fb7aa5fbb46f Reviewed-on: https://go-review.googlesource.com/c/go/+/417594 Run-TryBot: Bryan Mills <bcmills@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com> TryBot-Result: Gopher Robot <gobot@golang.org>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes: it reproduces with
go1.18.4
, but not withgo1.17.12
(because the latter does not support workspaces).What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
In the workspace given below, run:
txtar
workspaceWhat did you expect to see?
An error mentioning
GOPROXY=off
, like the one produced bygo1.17.12
but ideally cleaner:What did you see instead?
The
go list
command hangs indefinitely. Sending SIGQUIT gives the following goroutine dump, which looks to me like a livelock of some sort.This was found while investigating #51946.
The text was updated successfully, but these errors were encountered: