-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/net/http2: TestTransportBody* flaky on android and ppc64 #34616
Comments
I've seen the same behaviour on AWS CodeBuild, which is probably amd64. |
Still failing quite frequently on
Milestoned to 1.14 via #11811. |
cc @laboger |
I see this failure intermittently on ppc64le for both power8 and 9 as well as ppc64. It started soon after this: https://go-review.googlesource.com/c/net/+/181157, which is the change that added the test and the expected error message. |
|
Also on
|
|
I looked into this for a little bit. The test is somehow racing against the server's response to the header. It is trivial to reproduce to this by inserting a small pause before attempting to write the body.
|
Change https://golang.org/cl/234523 mentions this issue: |
Otherwise the server can stop the connection before clientStream.writeRequestBody has a chance to see if there is any more data beyond the specified content length. Tested by adding time.Sleep(time.Millisecond) to chunkReader.Read, which caused the test to reliably fail before this change, and reliably pass afterward. Fixes golang/go#34616 Change-Id: I119bdf01bf916b2ded2c5d293655cba2596c0166 Reviewed-on: https://go-review.googlesource.com/c/net/+/234523 Run-TryBot: Ian Lance Taylor <[email protected]> TryBot-Result: Gobot Gobot <[email protected]> Reviewed-by: Brad Fitzpatrick <[email protected]>
The
x/net/http2.TestTransportBody
tests seem to flake withrequest body larger than specified content length
errors at a relatively high rate on certain builders.Examples:
android-386-emu
:linux-ppc64-buildlet
CC @bradfitz @tombergan
The text was updated successfully, but these errors were encountered: