On Thu, 18 Sep 2025 11:47:45 GMT, Kevin Walls <kev...@openjdk.org> wrote:
> This test has failed due to a timing issue, but not continually or > reproducibly. > Looks like an effect of the TIMEOUT_FACTOR change (8260555). > > The recent failure has -J-Dtest.timeout.factor=1.0 and I see older logs > passing with -Dtest.timeout.factor=4.0 > > We should increase the timeout. As there have been occasional failures > before, looking back a few years, so multiply the current 500ms by a little > more than 4. This pull request has now been integrated. Changeset: 930d7249 Author: Kevin Walls <kev...@openjdk.org> URL: https://git.openjdk.org/jdk/commit/930d7249239e464adfca3a007342ce0fcb8f070d Stats: 5 lines in 1 file changed: 2 ins; 0 del; 3 mod 8367983: javax/management/monitor/ThreadPoolTest.java and StartStopTest.java fail with Unexpected Maximum Pool Size Overflow! Reviewed-by: cjplummer, dholmes ------------- PR: https://git.openjdk.org/jdk/pull/27361
