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.
-------------
Commit messages:
- 8379699: H3ConnectionPoolTest::testH2H3WithTwoAltSVC fails intermittently
Changes: https://git.openjdk.org/jdk/pull/30227/files
Webrev: https://webrevs.openjdk.org/?repo=jdk&pr=30227&range=00
Issue: https://bugs.openjdk.org/browse/JDK-8379699
Stats: 42 lines in 1 file changed: 6 ins; 22 del; 14 mod
Patch: https://git.openjdk.org/jdk/pull/30227.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/30227/head:pull/30227
PR: https://git.openjdk.org/jdk/pull/30227
