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: gotest fails with -ipv6=true option #1767

Closed
mikioh opened this issue May 2, 2011 · 1 comment

Comments

Projects
None yet
3 participants
@mikioh
Copy link
Contributor

commented May 2, 2011

What steps will reproduce the problem?
1. enable IPv6 connectivity on your node under test
2. run gotest ipv6=true from go/src/pkg/net
3.

What is the expected output?
PASS displayed

What do you see instead?
--- FAIL: net.TestDialGoogle (152.72 seconds)
    -- 64.233.183.106:80 --
    -- www.google.com:80 --
    -- 64.233.183.106:http --
    -- www.google.com:http --
    -- 064.233.183.106:0080 --
    -- [::ffff:64.233.183.106]:80 --
    -- [::ffff:40e9:b76a]:80 --
    -- [0:0:0:0:0000:ffff:64.233.183.106]:80 --
    -- [0:0:0:0:000000:ffff:64.233.183.106]:80 --
    -- [0:0:0:0:0:ffff::64.233.183.106]:80 --
    -- [2001:4860:0:2001::68]:80 --
    Dial("tcp", "", "[2001:4860:0:2001::68]:80") = _, dial tcp [2001:4860:0:2001::68]:80: operation timed out
    Dial("tcp6", "", "[2001:4860:0:2001::68]:80") = _, dial tcp6 [2001:4860:0:2001::68]:80: operation timed out
FAIL
gotest: "./6.out -ipv6=true" failed: exit status 1

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

Which operating system are you using?

Which revision are you using?  (hg identify)
2f0fa51fa2da tip

% hg summary
parent: 8257:2f0fa51fa2da tip
 weekly.2011-04-27
branch: default
commit: (clean)
update: (current)

Please provide any additional information below.
@rsc

This comment has been minimized.

Copy link
Contributor

commented May 2, 2011

Comment 1:

This issue was closed by revision 756df8e.

Status changed to Fixed.

@mikioh mikioh added fixed labels May 2, 2011

@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.