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
x/net/ipv6: apparent deadlock in TestPacketConnConcurrentReadWriteUnicast on darwin/amd64 #50455
Comments
It is always the reader that gets stuck, but sometimes it is the |
This output is consistent with what would happen if a writer goroutine errors out before writing. The |
Change https://golang.org/cl/376094 mentions this issue: |
A guess: perhaps the writers are failing with |
Change https://golang.org/cl/376095 mentions this issue: |
(Marking as release-blocker via #11811.) |
…ReadWriteUnicast This avoids a deadlock (observed in golang/go#50455) that may otherwise swallow the error logs from a failure, which may help us better diagnose the underlying problem. For golang/go#50455. Change-Id: Id73bd9589ae23385a433da0b24840ef945601f63 Reviewed-on: https://go-review.googlesource.com/c/net/+/376094 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
…ReadWriteUnicast This avoids a deadlock (observed in golang/go#50455) that may otherwise swallow the error logs from a failure, which may help us better diagnose the underlying problem. For golang/go#50455. Change-Id: Id73bd9589ae23385a433da0b24840ef945601f63 Reviewed-on: https://go-review.googlesource.com/c/net/+/376094 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
This change is sheer speculation based on the failures observed in golang/go#37319. (A deadlock in the test prevented us from seeing the actual failure mode of golang/go#50455 up until CL 376094, and it isn't obvious to me that we should wait for another failure before trying a likely — and otherwise harmless — fix.) Fixes golang/go#50455. (Maybe.) Change-Id: I7483eb2243832d07cb1f815da196b3978a50c6b3 Reviewed-on: https://go-review.googlesource.com/c/net/+/376095 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org>
greplogs --dashboard -md -l -e '(?ms)panic: test timed out.*\nsync\.\(\*WaitGroup\)\.Wait.*\n\t.*\ngolang\.org/x/net/ipv6_test.testPacketConnConcurrentReadWriteUnicast' --since=2021-01-01
2022-01-05T16:44:50-5b0dc2d-002283e/darwin-amd64-12_0
2021-11-11T16:01:37-58aab5e-3729a67/darwin-amd64-11_0
2021-10-05T18:39:53-d4b1ae0-7e69c5d/darwin-amd64-11_0
2021-10-01T17:27:29-e81a3d9-3357624/darwin-amd64-10_14
2021-09-27T18:44:47-4e4d966-d4007ae/darwin-amd64-10_14
2021-09-24T15:19:03-3ad01bb-7d57324/darwin-amd64-11_0
2021-08-24T16:55:17-60bc85c-daa55b2/darwin-amd64-10_14
2021-03-15T14:36:23-e18ecbb-7bfe32f/darwin-amd64-10_14
CC @ianlancetaylor
The text was updated successfully, but these errors were encountered: