-
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/http: TestTransportReuseConnection_Gzip_.* failures with "didn't reuse connection" #53373
Comments
if noone else does, i'll take a look this afternoon. assigning to myself as a reminder. |
i can't reproduce; will try to set up the same environment: |
@ayang64, given that there is only one of these in the logs, this looks to me to be a very rare failure. I would not expect it to reproduce easily. (That's why I suggest starting by modifying the test to dump more information — since this failure mode is so rare, ideally we should extract as much information as we can should it occur again.) |
This does not appear to be freebsd-specific: Note that |
Change https://go.dev/cl/432375 mentions this issue: |
These tests are flaky; add some additional logging in hopes it will aid in debugging. For #53373 Change-Id: I971a2815f50932a9700ef8c2f684c5416951e6de Reviewed-on: https://go-review.googlesource.com/c/go/+/432375 Reviewed-by: Bryan Mills <[email protected]> Run-TryBot: Damien Neil <[email protected]> TryBot-Result: Gopher Robot <[email protected]>
Added a watchflakes stanza to the issue description. |
Found new dashboard test flakes for:
2022-08-16 16:27 darwin-amd64-nocgo go@a45bbeae net/http.TestTransportReuseConnection_Gzip_Chunked (log)
|
(Still waiting for a flake with the additional tracing; the one at a45bbea predates the tracing.) |
This comment was marked as off-topic.
This comment was marked as off-topic.
I suspect this was fixed by https://go.dev/cl/483116. Closing as “probably fixed”, and |
greplogs -l -e 'FAIL: TestTransportReuseConnection.*(?:\n .*)* didn'\''t reuse connection' --since=2022-01-01
2022-06-08T19:41:54-bdde41e/freebsd-amd64-race
See previously #22212.
Perhaps a good first step would be to modify the test to use
net/http/httptrace
to dump more information about what's going on with the connections?(CC @neild @golang/freebsd)
The text was updated successfully, but these errors were encountered: