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

net: dial occasionally fails when kern.ipc.soconnect_async=1 on dragonfly #7541

Closed
mikioh opened this issue Mar 14, 2014 · 4 comments
Closed

net: dial occasionally fails when kern.ipc.soconnect_async=1 on dragonfly #7541

mikioh opened this issue Mar 14, 2014 · 4 comments
Labels
FrozenDueToAge
Milestone
Go1.3

Comments

@mikioh
Copy link
Contributor

mikioh commented Mar 14, 2014 

The buildbot says:

http://build.golang.org/log/52da4cf109770e1b2e7338e3df0882349b5190b3
--- FAIL: TestVariousDeadlines4Proc (75.00 seconds)
    timeout_test.go:480: 1ns run 1/1
    timeout_test.go:484: Dial: dial tcp 127.0.0.1:3913: operation timed out

and/or

http://build.golang.org/log/5633c87083c46fb7ba3fd0876c6e93a10b2db2d1
--- FAIL: TestTCPConcurrentAccept-256 (75.00 seconds)
        tcp_test.go:469: Dial failed: dial tcp 127.0.0.1:4696: operation timed out

We know that the 75s means net.inet.tcp.keepinit=75000, so something wrong happened on
dragonfly.
@mikioh
Copy link
Contributor Author

mikioh commented Mar 14, 2014

Comment 1:

This issue is the follower of issue #7474.

@mikioh
Copy link
Contributor Author

mikioh commented Mar 26, 2014

Comment 2:

This issue was updated by revision d1e3ad8.

Update issue #7474
LGTM=jsing
R=jsing
CC=golang-codereviews
https://golang.org/cl/75930043

@mikioh
Copy link
Contributor Author

mikioh commented Mar 26, 2014

Comment 3:

I (almost) give up. Looks like DragonFly BSD's pcb management sticks to rules, probably
for its SMP nature, anyway not easy to make it flexible without reconfiguring kernel
state via sysctl or using socket options. In conclusion, tweaking portrange during test
run would make sense (that's what I'm planning for Go 1.4, sigh).

@mikioh
Copy link
Contributor Author

mikioh commented Mar 29, 2014

Comment 4:

This issue was closed by revision 83ac901.

Status changed to Fixed.

@rsc rsc added this to the Go1.3 milestone Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 25, 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
Go1.3
Development

No branches or pull requests
3 participants
@mikioh @rsc @gopherbot