Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
net: TestDialCancel is flaky on linux/arm64-buildlet #15191
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,
pushed a commit
Apr 12, 2016
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: