-
Notifications
You must be signed in to change notification settings - Fork 18k
x/net/http2: TestContentEncodingNoSniffing failures with "connection reset by peer" #46762
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
Comments
Turns out not to be specific to PPC64, so this is looking like a flaky test or
2022-01-21T00:39:55-0dd24b2-32636cd/linux-amd64-clang |
These failures do not appear to be specific to a single subtest. |
The subtests of this test share a single @neild, could that cause this failure mode if two of the |
This comment has been minimized.
This comment has been minimized.
Setting
|
Change https://golang.org/cl/380154 mentions this issue: |
Marking as release-blocker: this test empirically affects multiple first-class ports, and I've mailed what I believe to be a fix. |
…o outlive the serverTester This test constructed a new serverTester for each subtest, but reused a Transport across all of the tests. I don't fully understand why, but for some reason that occasionally led to "connection reset by peer" failures when the port was reused. Scoping the Transport to the lifetime of the serverTester seems to resolve the errors: I tested with go test ./http2 -run=TestContentEncodingNoSniffing -httptest.serve=127.0.0.1:8080 -count=10000 and got lots of failures prior to this change and none after. Fixes golang/go#46762 (I hope.) Change-Id: I385c077c1d8627e42ce4d2db041878aacb5452fb Reviewed-on: https://go-review.googlesource.com/c/net/+/380154 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Damien Neil <dneil@google.com>
…o outlive the serverTester This test constructed a new serverTester for each subtest, but reused a Transport across all of the tests. I don't fully understand why, but for some reason that occasionally led to "connection reset by peer" failures when the port was reused. Scoping the Transport to the lifetime of the serverTester seems to resolve the errors: I tested with go test ./http2 -run=TestContentEncodingNoSniffing -httptest.serve=127.0.0.1:8080 -count=10000 and got lots of failures prior to this change and none after. Fixes golang/go#46762 (I hope.) Change-Id: I385c077c1d8627e42ce4d2db041878aacb5452fb Reviewed-on: https://go-review.googlesource.com/c/net/+/380154 Trust: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Damien Neil <dneil@google.com>
2021-06-14T18:27:18-04defd4/linux-ppc64le-buildlet
2021-04-05T18:03:19-a5a99cb/linux-ppc64-buildlet
2021-03-31T06:09:03-cb1fcc7/linux-ppc64le-power9osu
2021-03-29T18:18:59-df645c7/linux-ppc64le-buildlet
CC @neild @tombergan @laboger
It's not clear to me whether this is a flaky Go test or a platform bug.
The text was updated successfully, but these errors were encountered: