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: windows TestDialTimeout flake #11474

Closed
bradfitz opened this issue Jun 29, 2015 · 5 comments

Comments

Projects
None yet
5 participants
@bradfitz
Copy link
Member

commented Jun 29, 2015

Noticed this flake:
http://build.golang.org/log/de2ea0b431bc216003fd8762e62bbd46b3511fca

...
ok      math/rand   5.305s
ok      mime    1.365s
ok      mime/multipart  2.470s
ok      mime/quotedprintable    3.075s
--- FAIL: TestDialTimeout (0.00s)
    timeout_test.go:82: #3: dial tcp 127.0.0.1:0: connectex: The requested address is not valid in its context.
FAIL
FAIL    net 21.902s
ok      net/http    10.666s
ok      net/http/cgi    6.718s
ok      net/http/cookiejar  1.583s
...

/cc @alexbrainman @mikioh

@bradfitz bradfitz added this to the Go1.5Maybe milestone Jun 29, 2015

@alexbrainman

This comment has been minimized.

Copy link
Member

commented Jul 2, 2015

I run the test 100 times. It never breaks. The error is WSAEADDRNOTAVAIL.

Alex

@bradfitz

This comment has been minimized.

Copy link
Member Author

commented Jul 2, 2015

Did you run all the net tests, or just that one? Maybe there are interactions with other tests in the package.

@alexbrainman

This comment has been minimized.

Copy link
Member

commented Jul 3, 2015

I run "go test -short" in a loop now. No errors.

Alex

@rsc

This comment has been minimized.

Copy link
Contributor

commented Jul 15, 2015

Closing. If it happens again, reopen.

@mikioh

This comment has been minimized.

Copy link
Contributor

commented Aug 1, 2015

This is a duplicate of #11872.

@mikioh mikioh modified the milestones: Go1.5, Go1.5Maybe Aug 1, 2015

@golang golang locked and limited conversation to collaborators Aug 5, 2016

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.