net/http: deadlock after leaked transport detected in TestConsumingBodyOnNextConn #42943
Comments
Marking as release-blocker for 1.16 at least until we understand whether this is a regression. (CC @golang/release) |
I believe this issue is unrelated to the recent change I submitted. My change only modifies how |
As far as I can tell, the affected test also doesn't use |
Ah I see, the test I submitted isn't closing |
Actually nvm, the body is being closed above before being asserted into a |
So in order for the |
Most likely related to #42942 given the goroutine stuck on line 2605. |
/cc @neild |
Labeling as okay-after-beta1, but still considering this a release blocking issue. Please comment if you disagree. |
2020-12-01T21:42:10-7fca39a/linux-386-longtest
This is the only failure in the logs matching the regexp
(?ms)Test appears to have leaked a Transport.*test timed out
. It may be a secondary failure mode associated with #42942, or a different regression from CL 213277, or a latent bug that just happened to turn up now.CC @neild @fraenkel @bradfitz @nhooyr
The text was updated successfully, but these errors were encountered: