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: TestDialCancel is flaky on ARM and MIPS builders #15191
Comments
Odd:
Why would it return ENETUNREACH, but only sometimes? Amusingly, getsockopt's man page (http://linux.die.net/man/2/getsockopt) doesn't even mention this error. |
If you look at the code in netFD.connect in fd_unix.go, you'll see that (most likely) getsockopt is not returning ENETUNREACH. Instead, getsockopt(SO_ERROR) is succeeding in retrieving the error associated with the socket, and that error is ENETUNREACH. The error is really coming from connect, and it means that there is no route to the IP address. |
I'm just going to disable this test for now. I think that machine (on Linaro) has different routes than we've normally assumed for tests. For the record,
|
These builders (on Linaro) have a different network configuration which is incompatible with this test. Or so it seems. Updates #15191 Change-Id: Ibfeacddc98dac1da316e704b5c8491617a13e3bf Reviewed-on: https://go-review.googlesource.com/21901 Reviewed-by: Matthew Dempsky <mdempsky@google.com>
I've started seeing these as well on freebsd-arm-paulzhol: I'm not sure why it started appearing now. There have been some changes in the environment: switched to a buildlet based builder, upgrade to FreeBSD 11.1 etc. But they don't seem to be related. For my setup I can track the cause to the router/firewall replying with a TCP RST segment when dialing to the
It is OpenBSD pf firewall's recommended behavior according to https://www.openbsd.org/faq/pf/example1.html:
Where
|
Another one on |
|
The test assumes that trying to connect to 198.18.0.254 or 2001:2::254 will hang. I guess that is usually true, and I guess that it is not always true. I will send a CL to tweak the test. |
Change https://golang.org/cl/205698 mentions this issue: |
The text was updated successfully, but these errors were encountered: