This is not #50027: This test is expecting net.Conn.Close to have been called, which happens synchronously in CloseIdleConnections, not for the connection goroutines to have returned.
The only thing that makes sense is that a request has stayed live past Response.Body.Close being called (and is thus holding the connection live), which can happen in general, but I don't see how it happens in this test.
Flakes are super rare, and I haven't managed to reproduce it. Sent a CL to enable verbose HTTP/2 logging during this test; perhaps that'll point us at the problem the next time this flakes.
This test is very, very rarely flaky. Enable additional logs to help
debug what's going on.
Reviewed-by: Bryan Mills <email@example.com>
Reviewed-by: Brad Fitzpatrick <firstname.lastname@example.org>
Run-TryBot: Damien Neil <email@example.com>
TryBot-Result: Gopher Robot <firstname.lastname@example.org>