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.

Sign up for GitHub

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: TestDialerLocalAddr is flaky on Dragonfly #37359

Closed
bcmills opened this issue Feb 21, 2020 · 3 comments
Closed

net: TestDialerLocalAddr is flaky on Dragonfly #37359

bcmills opened this issue Feb 21, 2020 · 3 comments
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Dragonfly
Milestone
Backlog

Comments

@bcmills
Copy link
Contributor

bcmills commented Feb 21, 2020 

--- FAIL: TestDialerLocalAddr (75.00s)
    dial_test.go:658: tcp 127.0.0.1:0->127.0.0.1: got dial tcp 127.0.0.1:0->127.0.0.1:50318: connect: operation timed out; want <nil>
FAIL
FAIL	net	113.257s

This symptom is the same as observed on the Darwin builders in #22019.
This test is also flaky on FreeBSD, but with a different failure mode (#34264).

CC @mikioh @bradfitz @ianlancetaylor @tuxillo

2020-02-21T02:29:11-6dd11bc/dragonfly-amd64-5_6
2019-11-12T17:55:14-8c5dbba/dragonfly-amd64
2019-10-26T08:29:23-5d000a8/dragonfly-amd64-5_6
2019-10-25T23:25:31-1b79afe/dragonfly-amd64-5_6
2019-10-14T21:23:34-50f1157/dragonfly-amd64
2019-10-03T18:08:32-c33d45a/dragonfly-amd64
2019-09-27T15:38:16-5573885/dragonfly-amd64
2019-09-20T08:06:51-bb0a8fd/dragonfly-amd64
2019-08-28T04:43:53-b9ef4c0/dragonfly-amd64
2019-08-26T16:39:30-bc405df/dragonfly-amd64
2019-08-09T20:26:42-9c1f14f/dragonfly-amd64
2019-07-30T20:16:40-2fc7574/dragonfly-amd64
2019-05-20T20:58:14-ab724d4/dragonfly-amd64
2019-05-06T20:09:58-e1f9e70/dragonfly-amd64
@bcmills bcmills added OS-Dragonfly NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Feb 21, 2020
@bcmills bcmills added this to the Backlog milestone Feb 21, 2020
@tuxillo
Copy link
Contributor

tuxillo commented Feb 25, 2020

There has been some investigation going on, we're not sure yet what's the problem. When you say the test is flaky you mean it tends to fail in DragonFly or that the test itself has some issues?

@bcmills
Copy link
Contributor Author

bcmills commented Feb 25, 2020 •
edited

I mean that the test is observed to fail nondeterministically on this platform.

It is not obvious to me whether the bug is in the Dragonfly kernel, the Go standard library, or the test itself.

@bcmills
Copy link
Contributor Author

bcmills commented Jun 8, 2021

FAIL: TestDialerLocalAddr.*\n.*operation timed out:
2020-02-22T15:33:55-1894842/dragonfly-amd64
2020-02-21T02:29:11-6dd11bc/dragonfly-amd64-5_6
2019-11-12T17:55:14-8c5dbba/dragonfly-amd64
2019-10-26T08:29:23-5d000a8/dragonfly-amd64-5_6
2019-10-14T21:23:34-50f1157/dragonfly-amd64
2019-10-03T18:08:32-c33d45a/dragonfly-amd64
2019-09-27T15:38:16-5573885/dragonfly-amd64
2019-09-20T08:06:51-bb0a8fd/dragonfly-amd64
2019-08-28T04:43:53-b9ef4c0/dragonfly-amd64
2019-08-26T16:39:30-bc405df/dragonfly-amd64
2019-08-09T20:26:42-9c1f14f/dragonfly-amd64
2019-07-30T20:16:40-2fc7574/dragonfly-amd64
2019-05-20T20:58:14-ab724d4/dragonfly-amd64
2019-05-06T20:09:58-e1f9e70/dragonfly-amd64

No new failures in over a year, so I'm guessing this was a Dragonfly kernel bug that got fixed by a subsequent upgrade.

@bcmills bcmills closed this as completed Jun 8, 2021
@golang golang locked and limited conversation to collaborators Jun 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Dragonfly
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@tuxillo @bcmills @gopherbot