Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
net: network failure different on 386 vs amd64 #1447
from golang-nuts why are they different? ---------- Forwarded message ---------- From: email@example.com <firstname.lastname@example.org> Date: Wed, Jan 26, 2011 at 10:56 Subject: [go-nuts] Build failing in different ways on 386 and x86_64 build on same issue To: golang-nuts <email@example.com> Building the current version of go updated from the repository just minutes ago. One build on x86_64 the other on a 386 system both are Fedora 14. The failure is in the network tests, the site it tries to connect to is 220.127.116.11 which for whatever reason I'm unable to connect to. On the x86_64 system the build just hangs at that point, the 386 system fails and exits the build. Looks to me like there must be a difference in the build error handling between the 2, shouldn't they both fail the same way when they are failing on the same error?
I'm sorry for leaving this so long. I tried to reproduce this today, connecting to 18.104.22.168 and to 22.214.171.124, and both address hung during the TCP connect, both on 32-bit and 64-bit systems. It's really up to the TCP stack to decide whether to fail quickly or to take a long time, so it's hard to believe that 32- or 64-bit would matter. Marking as invalid since I cannot reproduce this. If you can still reproduce this on your system, please run the programs under strace -f -o trace.out and attach traces for both 32-bit and 64-bit execution, so we can see what the system calls are doing. Thanks.
Status changed to Invalid.