On Thu, 12 Mar 2026 18:52:18 GMT, Daniel Fuchs <[email protected]> wrote:
> This is a JUnit test. It should be using `org.junit.jupiter.api.Assertions`, > not `jdk.test.lib.Asserts`. > Some of the assertions seem to be inverted - should be (expected, actual) > In this instance - the message should have been: > > > assertEquals expected: quic:1 but was: quic:3 > > > What I believe happened is that due to the slowness of the test caused by > fastdebug, the `quic:1` connection got closed in idle timeout before it could > be reused. This caused a new `quic:3` connection to be created and used. > Increasing the h3 idle timeout (and possibly the quic idle timeout) should > solve that. This pull request has now been integrated. Changeset: b6de5aed Author: Daniel Fuchs <[email protected]> URL: https://git.openjdk.org/jdk/commit/b6de5aed2c2a5493c089b7f8493e953b13e4c2fa Stats: 42 lines in 1 file changed: 6 ins; 22 del; 14 mod 8379699: H3ConnectionPoolTest::testH2H3WithTwoAltSVC fails intermittently Reviewed-by: syan, jpai ------------- PR: https://git.openjdk.org/jdk/pull/30227
