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

net/http: TestSetsRemoteAddr failure on linux/amd64 #4181

Closed
gopherbot opened this issue Oct 1, 2012 · 8 comments
Closed

net/http: TestSetsRemoteAddr failure on linux/amd64 #4181

gopherbot opened this issue Oct 1, 2012 · 8 comments
Milestone

Comments

@gopherbot
Copy link

by jshholland:

What steps will reproduce the problem?
If possible, include a link to a program on play.golang.org.
1. Checkout tip.
2. Run src/all.bash

What is the expected output?
Everything should be built successfully.

What do you see instead?
http://pastie.org/private/gdjx08s264s5azsom2a70qB

Which compiler are you using (5g, 6g, 8g, gccgo)?
n/a

Which operating system are you using?
Ubuntu 12.10 beta (quantal)
@gopherbot
Copy link
Author

Comment 1 by jshholland:

Fixed link: http://pastie.org/private/gdjx08s264s5azsom2a70q

@robpike
Copy link
Contributor

robpike commented Oct 2, 2012

Comment 2:

Those links do not work. Feel free to put the text in the issue right here.

Status changed to WaitingForReply.

@gopherbot
Copy link
Author

Comment 3 by jshholland:

--- FAIL: TestSetsRemoteAddr (0.00 seconds)
serve_test.go:477:   Expected local addr; got "redacted:39294"
FAIL
FAIL  net/http  2.412s

@gopherbot
Copy link
Author

Comment 4 by jshholland:

I tried testing a few old revisions more-or-less at random to try and find a bisect
start point last night, and they either failed to build for an unrelated reason, or had
the same error.
Ones that failed with the same issue:
13870:f979026319cc
13487:e2d931c0c0fc
12045:b96e722aad5a
11210:aa208a81cc08

@rsc
Copy link
Contributor

rsc commented Oct 6, 2012

Comment 5:

Labels changed: added priority-later, go1.1, removed priority-triage.

Status changed to Accepted.

@gopherbot
Copy link
Author

Comment 6 by jshholland:

The test now passes, although I have a new failure. I'll open a separate issue for that
one.

@gopherbot
Copy link
Author

Comment 7 by jshholland:

Apologies for the noise, I had forgotten that I commented out the failing test in my
checkout.

@davecheney
Copy link
Contributor

Comment 8:

Status changed to Retracted.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 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.
Projects
None yet
Development

No branches or pull requests

4 participants