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/http: TestTLSServerClosesConnection is flaky #7634
Labels
FrozenDueToAge
Testing
An issue that has been verified to require only test changes, not just a test failure.
Milestone
Comments
This issue was updated by revision aa2d4de. LGTM=alex.brainman R=adg, alex.brainman CC=golang-codereviews https://golang.org/cl/80110043 |
bradfitz
changed the title
net/http: TestTLSServerClosesConnection is flaky on Windows
net/http: TestTLSServerClosesConnection is flaky
Feb 2, 2016
Also failed on Darwin. Details in #14195 |
bradfitz
added
the
Testing
An issue that has been verified to require only test changes, not just a test failure.
label
Feb 1, 2017
Ran 200 runs on macOS Sierra: no problems. All pass 20/20:
Likewise with gomote on a Maybe this is no longer flaky. |
Closing until there are reports that this still happens. |
Change https://golang.org/cl/121735 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Aug 20, 2018
Issues #10043, #15405, and #22660 appear to have been fixed, and whatever tests I could run locally do succeed, so remove the skips. Issue #7237 was closed in favor of #17906, so update its skip line. Issue #7634 was closed as it had not appeared for over three years. Re-enable it for now. An issue should be open if the test starts being skipped again. Change-Id: I67daade906744ed49223291035baddaad9f56dca Reviewed-on: https://go-review.googlesource.com/121735 Run-TryBot: Daniel Martí <mvdan@mvdan.cc> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
FrozenDueToAge
Testing
An issue that has been verified to require only test changes, not just a test failure.
The text was updated successfully, but these errors were encountered: