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: TestAcceptTimeout still flaky #17948
Comments
CL https://golang.org/cl/33330 mentions this issue. |
CL https://golang.org/cl/33258 mentions this issue. |
Nope. Still flaky: freebsd-amd64-gce101 at 81627f0 https://build.golang.org/log/c69b9de990f663a7ea8e00a0f2b589365234aaba |
It's too flaky and doing more harm than good. Disable it until it can be made reliable. Updates #17948 Updates #17927 Change-Id: Iaab7f09a4060da377fcd3ca2262527fef50c558d Reviewed-on: https://go-review.googlesource.com/33330 Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
That's a different issue. We fixed two issues: a) context-based canceling based on defer function execution behaves differently than previous versions on Darwin and FreeBSD, b) TCP control segments for active close operation at passive open side don't deliver immediately on Darwin, and now have c) "dial tcp 127.0.0.1:42120: i/o timeout" at active open side. It's fine to move forward step by step, I'm not sure why the test starts behaving unbridledly during Go 1.8 development cycle, though. Does Go 1.8 contain massive changes to runtime, net or testing packages? |
In any case, it's still flaky.
There have certainly been runtime changes. You would know whether there have been net changes. I don't think there have been notable testing changes. |
Change https://golang.org/cl/105095 mentions this issue: |
TestAcceptTimeout
is still flaky:https://build.golang.org/log/74ef15095b884eff2e47c1d1ed91a7643c2424cb
I'm just going to disable it for now. It's doing more harm than good.
The text was updated successfully, but these errors were encountered: