-
Notifications
You must be signed in to change notification settings - Fork 18k
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: TestReadTimeout flake #14986
Comments
/cc @mikioh |
In general, when the runtime or compiler stuff is under heavy development, some tests in the net package usually become unstable because the net package heavily depends on fancy stuff provided by runtime such as read/write semaphores, timers and I/O event notification and scheduling mech. Please ping me when the failure happens after the Go 1.7 development cutoff day. |
On the contrary, now (earlier) is the time to de-flake tests, and to help find any runtime problems. |
Well then, @Thomasdezeeuw, can you tell us a bit more details?
If you have a spare time and the failure is reproducible, please run
If you have more spare time, the trace of kevent by using dtrace would be a great help. See dtrace(1) on OS X. Thanks. |
@mikioh OS X version |
An update, I ran |
I updated go and build it from source again, running
Is there a reason why The full build log: build3.txt. |
I modified
|
Running
|
Please let us know which rev. of Go you are using (git rev-parse HEAD). Otherwise, we need to play a guessing game. If you are not confident and have no evidence that the issues you encountered have the same root cause:
|
Please show us the entire stack trace. Also which rev. of Go? |
@mikioh Sorry about that, I'm at
|
Thanks for the information. My guess is that:
I guess that the following patch might mitigate the failures.
Just tried |
@mikioh I ran the tests for 2 hours and had no failure's, that change seems to work. |
Please answer these questions before submitting your issue. Thanks!
go version
)?go version devel +4ffa5eb Sun Mar 27 05:31:54 2016 +0000 darwin/amd64
.go env
)?ran
all.bash
.Successful build.
Two build failures, a third build correctly.
First failed test.
Second build error, with even less information.
See attached logs for the complete logs.
build.txt
build2.txt
The text was updated successfully, but these errors were encountered: