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

Jump to bottom

gccgo, net: dial_test.go:75: all connections connected; expected some to time out #3307

Closed
alberts opened this issue Mar 13, 2012 · 10 comments
Closed

gccgo, net: dial_test.go:75: all connections connected; expected some to time out #3307

alberts opened this issue Mar 13, 2012 · 10 comments
Labels
FrozenDueToAge

Comments

@alberts
Copy link
Contributor

alberts commented Mar 13, 2012 

What steps will reproduce the problem?

make check-target-libgo

What is the expected output?

test pass

What do you see instead?

--- FAIL: net.TestDialTimeout (0.17 seconds)
dial_test.go:75: all connections connected; expected some to time out
FAIL
FAIL: net

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

gccgo

Which operating system are you using?

linux, 64-bit build

Which revision are you using?  (hg identify)

commit 7714837c8d8c66a53d87e4de6818fe47e1bb51d3
Date: Fri Mar 9 11:49:50 2012 +0000
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@185136
138bc75d-0d04-0410-961f-82ee72b054a4

Please provide any additional information below.

Test fails quite quickly (0.17 seconds). Maybe a clue?
@ianlancetaylor
Copy link
Contributor

Comment 1:

Does this happen consistently?

Labels changed: added priority-go1, gccgo, removed priority-triage.

@alberts
Copy link
Contributor Author

alberts commented Mar 13, 2012

Comment 2:

No, this is an intermittent thing.

@ianlancetaylor
Copy link
Contributor

Comment 3:

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

@ianlancetaylor
Copy link
Contributor

Comment 4:

I'm not having much luck recreating this on Ubuntu Lucid.  I can't recall ever seeing
this error.
What distro are you running?  What kernel version?  What is the contents of the file
/proc/sys/net/core/somaxconn ?

Owner changed to @ianlancetaylor.

@alberts
Copy link
Contributor Author

alberts commented Apr 25, 2012

Comment 5:

Fedora 16 x86-64. 3.something at the time I reported this. I'll check somaxconn and
rerun the tests to see if I can still reproduce.

@ianlancetaylor
Copy link
Contributor

Comment 6:

I just tried a Fedora 16 x86_64 system, but I had no luck reproducing it there either.
You didn't mention the contents of /proc/sys/net/core/somaxconn.

@alberts
Copy link
Contributor Author

alberts commented Jul 26, 2012

Comment 7:

Just hit this issue with 6g too. issue #3867.

@alberts
Copy link
Contributor Author

alberts commented Jul 26, 2012

Comment 8:

/proc/sys/net/core/somaxconn is 128

@rsc
Copy link
Contributor

rsc commented Sep 12, 2012

Comment 9:

Status changed to Accepted.

@bradfitz
Copy link
Contributor

Comment 10:

This issue was closed by revision cdc6424.

Status changed to Fixed.

mikioh pushed a commit that referenced this issue Apr 2, 2015
@cixtor
net: deflake TestDialTimeout
8b0e38f 
This change makes TestDialTimeout work on almost all the supported
platforms.

Updates #3016.
Updates #3307.
Updates #3867.
Updates #5380.
Updates #5349.

Change-Id: Iacf0ebea23cdd8f6c0333d70c667a5a5f5eb0ed2
Reviewed-on: https://go-review.googlesource.com/8220
Reviewed-by: Ian Lance Taylor <iant@golang.org>
@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.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@bradfitz @rsc @alberts @ianlancetaylor @gopherbot