On Thu, 6 Nov 2025 16:22:41 GMT, Daniel Fuchs <[email protected]> wrote:
> Nothing looks wrong with the test or the code. The failure happens rarely - > probably when the machine is under load: this test tries to saturate the > socket buffers and is resource consuming. > > The proposed fix is just to double the jtreg timeout for this test from 120 > to 240. a FYI on this timeout ... current timeout factor == 4 i.e. test timeout is 120 * 4 == 480 seconds as per test log -J-Dtest.timeout.factor=4.0 so you are effectively increasing from 120 * 4 to 240 * 4 ------------- PR Comment: https://git.openjdk.org/jdk/pull/28178#issuecomment-3498472889
