On Thu, 25 Sep 2025 15:54:42 GMT, Daniel Fuchs <[email protected]> wrote:
> Hi, > > The H3ServerPushTest.java has been observed failing once in the CI on a > personal job. > Analysis reveals that the test actually passed, but the timeout handler > killed the test. > > > SUCCESSFUL > H3ServerPushTest::testExcessivePushResponsesWithDistinctIdsInOneResponse > 'testExcessivePushResponsesWithDistinctIdsInOneResponse(TestInfo)' [2840ms] > > [ JUnit Containers: found 4, started 4, succeeded 4, failed 0, aborted 0, > skipped 0] > [ JUnit Tests: found 17, started 17, succeeded 17, failed 0, aborted 0, > skipped 0] > > JavaTest Message: Test complete. > ... > result: Error. "junit" action timed out with a timeout of 120 seconds on > agent 23 > > test result: Error. "junit" action timed out with a timeout of 120 seconds on > agent 23 > > > This is probably attributable to the change of timeoutFactor to > timeoutFactor=1, this change proposes to use othervm double the default > timeout for that test to `/othervm/timeout=240` . This pull request has now been integrated. Changeset: 7ad9bdef Author: Daniel Fuchs <[email protected]> URL: https://git.openjdk.org/jdk/commit/7ad9bdef1ed250a824ee9dee69b37bbcc8f7c924 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod 8368630: java/net/httpclient/http3/H3ServerPushTest.java succeeds but fails in jtreg timeout Reviewed-by: syan, jpai ------------- PR: https://git.openjdk.org/jdk/pull/27492
