-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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: TestDialerLocalAddr and TestNetpollDeadlock are flaky on macOS 10.12 #22019
Comments
CC @mikioh |
Here are some failures from the builders:
|
Change https://golang.org/cl/86000 mentions this issue: |
I don't know why these errors occur. Ignore them to avoid breaking the build. Updates #22019 Change-Id: Ia048e6d9b928e8e237b311ff3a364e7a23af4aa4 Reviewed-on: https://go-review.googlesource.com/86000 Run-TryBot: Ian Lance Taylor <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]>
#22403 was marked as a duplicate of this, and recurred in https://build.golang.org/log/b8eabc31874c5ab9c691a4a3e4dceb2c8656b16c:
|
|
@mikioh @bradfitz @ianlancetaylor, I think we need someone to look into this for 1.14. I'm worried about another case like #32336, where an occasional test flake turned out to be a symptom of a serious bug. |
|
|
|
#32919 may be related. |
As far as I can see all failures are on Darwin 10.12. There are no failures on newer versions. This makes me suspect that it is a kernel problem that was fixed. |
@ianlancetaylor, as far as I can tell that is indeed the case. Do you think 10.12 is in wide enough usage to warrant a workaround for the kernel issue? If not, should we skip |
I personally have no idea whether 10.12 is in wide use. I would be fine with a workaround but I don't have one. The test seems to be timing out waiting for a non-blocking |
In case it's helpful, this StatCounter Global Stats page suggests 10.12 is currently at just under 10% use, while 10.13 is at just over 20%, and 10.14 is at over 50%. (10.15 isn't on the chart yet; the latest entry is from September, before it was out.) |
To me that suggests that we should probably upgrade the |
Change https://golang.org/cl/202618 mentions this issue: |
What version of Go are you using (
go version
)?development (1.9+)
go version devel +4fa3d69e00 Fri Sep 22 14:03:36 2017 -0400 darwin/amd64
Does this issue reproduce with the latest release?
intermittently. That's the bug.
What operating system and processor architecture are you using (
go env
)?If you run run.bash repeatedly on a Mac, for instance running a binary search to isolate a single failing function, the test sometimes fails. This then causes the binary search to go down a false path and not work.
The text was updated successfully, but these errors were encountered: