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. @sendaoYan if you have a means to verify that this PR, as well as https://git.openjdk.org/jdk/pull/30224, solve these intermitent issues that will be appreciated. ------------- PR Comment: https://git.openjdk.org/jdk/pull/30227#issuecomment-4054588029
