-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: fatal error: all goroutines are asleep - deadlock!
since 2023-07-18
#61454
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-07-18 19:54 openbsd-386-72 tools@03275ec1 go@813aad51 x/tools/go/packages.TestParseFileModifyAST (log)
2023-07-18 19:55 linux-ppc64le-buildlet go@5d481abc runtime.TestFakeTime (log)
2023-07-18 21:24 darwin-amd64-13 go@813aad51 cmd/cgo/internal/test/issue24161e2 [build] (log)
2023-07-18 23:25 darwin-amd64-10_15 tools@84f829e2 go@5fe3f0a2 x/tools/gopls/internal/regtest/diagnostics.TestNoMod (log)
2023-07-18 23:25 darwin-amd64-12_0 tools@84f829e2 go@70072715 x/tools/gopls/internal/regtest/completion.TestPackageCompletion (log)
2023-07-18 23:25 openbsd-amd64-72 tools@84f829e2 go@cd6c4e05 x/tools/go/packages.TestConfigFlags (log)
2023-07-18 23:51 darwin-amd64-longtest go@8e1ec1cb cmd/vet.TestVet (log)
2023-07-18 23:51 freebsd-arm-paulzhol go@8e1ec1cb cmd/cgo/internal/test/issue30527 [build] (log)
2023-07-18 23:51 openbsd-386-72 go@8e1ec1cb cmd/go.TestScript (log)
|
Change https://go.dev/cl/511356 mentions this issue: |
This was most likely triggered by https://go.dev/cl/503923 for #60782. However, my current thinking is that that CL is just exposing a pre-existing bug and making it more likely to occur. Before that change, The scheduler has an optimization: it it doesn't bother to poll the network if The Before the CL, when Now that |
Change https://go.dev/cl/511455 mentions this issue: |
cc @ianlancetaylor
The text was updated successfully, but these errors were encountered: