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: socket: An address incompatible with the requested protocol was used error on windows #10787

Closed
alexbrainman opened this issue May 12, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@alexbrainman
Copy link
Member

commented May 12, 2015

C:\go\root\src\net>go test
--- FAIL: TestTCPListener (0.00s)
        listen_test.go:70: skipping tcp :: test
        listen_test.go:70: skipping tcp ::1 test
        listen_test.go:76: listen tcp6 :0: socket: An address incompatible with the requested protocol was used.
--- FAIL: TestUDPListener (0.02s)
        listen_test.go:131: skipping udp :: test
        listen_test.go:131: skipping udp ::1 test
        listen_test.go:137: listen udp6 :0: socket: An address incompatible with the requested protocol was used.
--- FAIL: TestLookupGoogleSRV (0.19s)
        lookup_test.go:54: got "google.com"; want ".google.com"
--- FAIL: TestLookupGooglePublicDNSAddr (0.95s)
        lookup_test.go:146: got "google-public-dns-a.google.com"; want a record containing ".google.com."
        lookup_test.go:146: got "google-public-dns-b.google.com"; want a record containing ".google.com."
        lookup_test.go:146: got "google-public-dns-a.google.com"; want a record containing ".google.com."
        lookup_test.go:146: got "google-public-dns-b.google.com"; want a record containing ".google.com."
FAIL
Leaked goroutines:
net.(*ioSrv).ProcessRemoteIO(0x10dcc350)
        c:/go/root/src/net/fd_windows.go:138 +0xcc
created by net.startServer
        c:/go/root/src/net/fd_windows.go:238 +0xcc
net.(*ioSrv).ProcessRemoteIO(0x10dcc358)
        c:/go/root/src/net/fd_windows.go:138 +0xcc
created by net.startServer
        c:/go/root/src/net/fd_windows.go:240 +0x121

Socket statistical information:
(inet4, stream, default): opened=748, connected=0, listened=54, accepted=0, closed=735, openfailed=0, connectfailed=291, listenfailed=0, acceptfailed=0, closefailed=0
(inet4, datagram, default): opened=82, connected=6, listened=0, accepted=0, closed=82, openfailed=0, connectfailed=0, listenfailed=0, acceptfailed=0, closefailed=0
(local, stream, default): opened=0, connected=0, listened=0, accepted=0, closed=0, openfailed=2, connectfailed=0, listenfailed=0, acceptfailed=0, closefailed=0
(local, datagram, default): opened=0, connected=0, listened=0, accepted=0, closed=0, openfailed=1, connectfailed=0, listenfailed=0, acceptfailed=0, closefailed=0
(inet6, stream, default): opened=0, connected=0, listened=0, accepted=0, closed=0, openfailed=1, connectfailed=0, listenfailed=0, acceptfailed=0, closefailed=0
(inet6, datagram, default): opened=0, connected=0, listened=0, accepted=0, closed=0, openfailed=1, connectfailed=0, listenfailed=0, acceptfailed=0, closefailed=0
(inet4, raw, 1): opened=2, connected=0, listened=0, accepted=0, closed=2, openfailed=0, connectfailed=0, listenfailed=0, acceptfailed=0, closefailed=0
(local, seqpacket, default): opened=0, connected=0, listened=0, accepted=0, closed=0, openfailed=2, connectfailed=0, listenfailed=0, acceptfailed=0, closefailed=0
(inet4, datagram, udp): opened=5, connected=0, listened=0, accepted=0, closed=5, openfailed=0, connectfailed=0, listenfailed=0, acceptfailed=0, closefailed=0

exit status 1
FAIL    net     49.849s

C:\go\root\src\net>go version
go version devel +77fc03f Tue May 12 01:30:40 2015 +0000 windows/386

I am not sure what is intended to fail, and what is meant to work.

Alex

@mikioh

This comment has been minimized.

Copy link
Contributor

commented May 12, 2015

Can you please file another issue for TestLookupXXX.

listen_test.go:76: listen tcp6 :0: socket: An address incompatible with the requested protocol was used.
listen_test.go:137: listen udp6 :0: socket: An address incompatible with the requested protocol was used.

Also which version of Windows are you running? These two are unexpected.

@mikioh mikioh changed the title net: running "go test" fails on windows net: socket: An address incompatible with the requested protocol was used error on windows May 12, 2015

@gopherbot

This comment has been minimized.

Copy link

commented May 12, 2015

CL https://golang.org/cl/9948 mentions this issue.

@alexbrainman

This comment has been minimized.

Copy link
Member Author

commented May 13, 2015

#10795 for TestLookupXXX. I am using Windows XP.

Alex

@mikioh mikioh closed this in 3b38626 May 13, 2015

@mikioh mikioh added this to the Go1.5 milestone May 23, 2015

@golang golang locked and limited conversation to collaborators Jun 25, 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.