> 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` .
Daniel Fuchs has updated the pull request incrementally with one additional commit since the last revision: Really change timeout ------------- Changes: - all: https://git.openjdk.org/jdk/pull/27492/files - new: https://git.openjdk.org/jdk/pull/27492/files/388db3dc..93df2f6f Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=27492&range=01 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=27492&range=00-01 Stats: 1 line in 1 file changed: 0 ins; 0 del; 1 mod Patch: https://git.openjdk.org/jdk/pull/27492.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/27492/head:pull/27492 PR: https://git.openjdk.org/jdk/pull/27492
