Skip to content
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

Jump to bottom

net: network failure different on 386 vs amd64 #1447

Closed
rsc opened this issue Jan 27, 2011 · 5 comments
Closed

net: network failure different on 386 vs amd64 #1447

rsc opened this issue Jan 27, 2011 · 5 comments
Labels
FrozenDueToAge
Milestone
Go1

Comments

@rsc
Copy link
Contributor

rsc commented Jan 27, 2011 

from golang-nuts

why are they different?


---------- Forwarded message ----------
From: bass.warrior@gmail.com <bass.warrior@gmail.com>
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 <golang-nuts@googlegroups.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 74.125.19.99 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?
@rsc
Copy link
Contributor Author

rsc commented Dec 9, 2011

Comment 1:

Labels changed: added priority-later.

@rsc
Copy link
Contributor Author

rsc commented Dec 12, 2011

Comment 2:

Labels changed: added priority-go1.

@robpike
Copy link
Contributor

robpike commented Jan 13, 2012

Comment 3:

Owner changed to builder@golang.org.

@rsc
Copy link
Contributor Author

rsc commented Jan 24, 2012

Comment 4:

Status changed to HelpWanted.

@rsc
Copy link
Contributor Author

rsc commented Feb 12, 2012

Comment 5:

I'm sorry for leaving this so long.  I tried to reproduce this today,
connecting to 8.8.4.4 and to 74.125.19.99, 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.

@rsc rsc added this to the Go1 milestone Apr 10, 2015
@rsc rsc removed the priority-go1 label Apr 10, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1
Development

No branches or pull requests
3 participants
@rsc @robpike @gopherbot