We recently enabled net/http tests for our internal x/net/internal/http3 implementation in https://go.dev/cl/765320. Unfortunately, the tests end up being flaky.
The flakes seem to be mostly coming from the following issues, in order of most to least prevalent (though there might be more):
- QUIC connections are not shutdown fast enough during test cleanup, causing them to be detected as goroutine leaks.
- x/net/quic has a race condition where its output buffer are written to without locks (synchronously and intentionally, for optimization), but may be asynchronously written when the QUIC stream receives a
STOP_SENDING frame.
- Similar to 2., but for input buffer, with data race between reading and closing the stream.
- Handshake timeout for unknown reasons when trying to establish TLS connection.
The HTTP/3 tests have therefore been temporarily disabled for now (https://go.dev/cl/766740). This is a bug to track the actual fix and to dedupe the many watchflake issues that were opened.
We recently enabled net/http tests for our internal x/net/internal/http3 implementation in https://go.dev/cl/765320. Unfortunately, the tests end up being flaky.
The flakes seem to be mostly coming from the following issues, in order of most to least prevalent (though there might be more):
STOP_SENDINGframe.The HTTP/3 tests have therefore been temporarily disabled for now (https://go.dev/cl/766740). This is a bug to track the actual fix and to dedupe the many watchflake issues that were opened.