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: TestDualStackUDPListener test failure #3301

Closed
bradfitz opened this issue Mar 12, 2012 · 5 comments

Comments

Projects
None yet
5 participants
@bradfitz
Copy link
Member

commented Mar 12, 2012

Sporadic test failure on linux-amd64

$ go test net

--- FAIL: TestDualStackUDPListener (0.00 seconds)
    unicast_test.go:429: Second ListenPacket("udp", "127.0.0.1:47036") returns listen udp 127.0.0.1:47036: address already in use, expected <nil>
FAIL
FAIL    net 1.161s


$ hg id
1c40c7aee4d6 tip
@rsc

This comment has been minimized.

Copy link
Contributor

commented Mar 12, 2012

Comment 1:

The test does a listen on [::1]:0, gets [::1]:47036, and then tries to listen
127.0.0.1:47036.
Maybe the IPv4 port really is in use.  There's no guarantee really.
I think this is fine to leave for after Go 1.

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

Status changed to Accepted.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Mar 13, 2012

Comment 2:

Sure, listens with each address family's specific address 
should be considered as listening on address family
independent port table.
@rsc

This comment has been minimized.

Copy link
Contributor

commented Sep 12, 2012

Comment 3:

Labels changed: added go1.1maybe.

@rsc

This comment has been minimized.

Copy link
Contributor

commented Mar 12, 2013

Comment 4:

[The time for maybe has passed.]

Labels changed: removed go1.1maybe.

@davecheney

This comment has been minimized.

Copy link
Contributor

commented Jun 15, 2013

Comment 5:

I haven't seen a failure of this kind, even on darwin, in months. Somewhere in the last
few months, this was fixed by accident.
Will reopen if it reoccurs.

Status changed to TimedOut.

@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.
You can’t perform that action at this time.