-
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
net/http: TestClientWriteShutdown failures on darwin-arm64-11_0-toothrot #49860
Comments
This looks to me like a deadlock, but (due to the use of an unnecessary and arbitrary timeout) the test is currently not producing useful goroutine dumps to diagnose it. We need to fix the test before we can fix the underlying deadlock. |
Marking as release-blocker for Go 1.19, rather than 1.18, because it appears to affect a single platform and it isn't obvious to me that we well have a useful goroutine dump to diagnose it before the 1.18 release. (I suspect that we will want to backport the fix once it is identified.) |
Change https://golang.org/cl/367615 mentions this issue: |
This test occasionally hangs on the darwin-arm64-11_0-toothrot builder. When it does, it fails with the unhelpful error message "timeout" instead of a useful goroutine dump. This change eliminates the use of an arbitrary timeout channel, so that if (and probably when) the test hangs again we will get more useful logs to diagnose the root cause. For #49860 Change-Id: I23f6f1c81209f0b2dbe565e1dfb26b1b2eff0187 Reviewed-on: https://go-review.googlesource.com/c/go/+/367615 Trust: Bryan C. Mills <[email protected]> Run-TryBot: Bryan C. Mills <[email protected]> TryBot-Result: Go Bot <[email protected]> Reviewed-by: Damien Neil <[email protected]>
Curiously, no repros since the timeout was removed. Maybe it wasn't a deadlock after all. 🤔
|
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Observed a recent failure on 1.17 release branch CL https://golang.org/cl/367615 didn't make into 1.17. So this is still observing old behavior. Not new, then. |
greplogs --dashboard -md -l -e 'FAIL: TestClientWriteShutdown .+\n .+: timeout'
2021-11-29T00:58:50-1ea4d3b/darwin-arm64-11_0-toothrot
2021-09-02T19:16:19-9633195/darwin-arm64-11_0-toothrot
2021-08-23T19:49:23-0a7f00a/darwin-arm64-11_0-toothrot
2021-05-28T18:36:54-6624771/darwin-arm64-11_0-toothrot
2021-05-09T00:07:34-ec4efa4/darwin-arm64-11_0-toothrot
2021-04-27T18:54:49-0ae9c3b/darwin-arm64-11_0-toothrot
2021-04-12T21:59:59-263e13d/darwin-arm64-11_0-toothrot
2021-03-18T00:23:25-51e4bb2/darwin-arm64-11_0-toothrot
2021-03-13T11:52:17-b3235b7/darwin-arm64-11_0-toothrot
(attn @neild)
The text was updated successfully, but these errors were encountered: