On Sun, 15 Mar 2026 14:27:04 GMT, SendaoYan <[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. > > After this proposed patch, > test/jdk/java/net/httpclient/http3/H3ConnectionPoolTest.java run all passed > 1000 times with fastdebug build. Thanks @sendaoYan and @jaikiran ------------- PR Comment: https://git.openjdk.org/jdk/pull/30227#issuecomment-4084001349
