On Sat, 8 Nov 2025 00:15:24 GMT, Serguei Spitsyn <[email protected]> wrote:
> This is fix is to increase the `EXPECTED_ACCURACY` value in the test: > `hotspot/jtreg/vmTestbase/nsk/jvmti/scenarios/contention/TC05/tc05t001`. > It is used check that the waiting time between `MonitorWait` and > `MonitorWaited` event is not big. It seems that in some corner cases this > time can be bigger than expected. > > Testing: > - TBD: Verify the test with mach5 test runs test/hotspot/jtreg/vmTestbase/nsk/jvmti/scenarios/contention/TC05/tc05t001/tc05t001.cpp line 43: > 41: > 42: #if (defined(WIN32) || defined(_WIN32)) > 43: static const jlong EXPECTED_ACCURACY = 32; // 16ms is longest clock > update interval Does the comment 16ms should be updated. ------------- PR Review Comment: https://git.openjdk.org/jdk/pull/28206#discussion_r2506407679
