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
runtime: timeouts in TestChan on netbsd-arm64-bsiegert and openbsd-arm64-jsing #52703
Comments
Curiously, a timeout in the same place on I'm not sure whether to approach this as a BSD bug, an
|
One today without the goroutine in the
|
|
@4a6f656c, I'm going to drop |
|
Change https://go.dev/cl/408703 mentions this issue: |
For golang/go#52653. Updates golang/go#52703. Change-Id: I0873c19865d17b387bfe7f7e2d21b3bb343d0855 Reviewed-on: https://go-review.googlesource.com/c/build/+/408703 TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Alex Rakoczy <alex@golang.org> Run-TryBot: Bryan Mills <bcmills@google.com> Auto-Submit: Bryan Mills <bcmills@google.com>
@bcmills are there any occurrences of this on openbsd-arm64-jsing prior to 2022-05-04? I believe this relates to an OpenBSD kernel issue, which if the answer to the above question is no, lines up with an upgrade to 7.1. I've just applied a kernel patch that should avoid the issue - hopefully we'll know in the near future. |
None that I could find.
Great! If you'd like to send a CL to remove the KnownIssue for the builder (https://cs.opensource.google/go/x/build/+/master:dashboard/builders.go;l=2135;drc=2305360635654c3c7c875b9e5f14e56463d9634a), we can put it back into triage to check for any remaining issues. |
Change https://go.dev/cl/410095 mentions this issue: |
greplogs -l -e 'goroutine \d+ \[sleep.*\]:\n(?:.+\n\t.+\n)*runtime_test\.TestChan' --since=2021-01-01
2022-05-03T19:48:07-bccce90/netbsd-arm64-bsiegert
2021-11-13T00:26:23-bc0b98e/netbsd-arm64-bsiegert
2021-09-23T20:15:19-93f964b/netbsd-arm64-bsiegert
2021-09-08T22:47:57-bff39cf/netbsd-arm64-bsiegert
It's not clear to me whether this is a deadlock or livelock in or exposed by this particular test, or an overall timeout due to a long stall in some other test function. (Note that
TestChan
is not parallel.)attn @bsiegert; CC @golang/runtime, @golang/netbsd
The text was updated successfully, but these errors were encountered: