-
Notifications
You must be signed in to change notification settings - Fork 18k
net: TestDialParallelSpuriousConnection occasionally times out #34495
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
Same failure mode on |
|
|
A different (but likely related) failure mode:
2020-02-29T17:02:40-74f8983/darwin-arm64-corellium |
More of the new failure mode: |
Actually, those new failures seem Corellium-specific. Opening a new issue. |
Change https://golang.org/cl/375694 mentions this issue: |
This is a recurring test failure and does not seem to be port-specific, so marking as release-blocker. I've mailed what I believe to be a fix. |
…ction The arbitrary sleep in this test is empirically not always long enough on slower builders. However, we know the exact number of connections that should be dialed: we can wait on that number in the dial hook instead. Fixes golang#34495 Change-Id: I538244ceb75a80271a724304b993309482bd5b41 Reviewed-on: https://go-review.googlesource.com/c/go/+/375694 Trust: Bryan Mills <[email protected]> Run-TryBot: Bryan Mills <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
From the
darwin-amd64-race
builder (https://build.golang.org/log/96aa6d382799b872cbedeb56e3b9d2076acc6546):It's not obvious to me whether the test was deadlocked or just ran out of time.
If the latter, perhaps some of its tests should be skipped in short mode (and/or when the race detector is enabled)?
CC @mikioh @bradfitz @ianlancetaylor
The text was updated successfully, but these errors were encountered: