On Tue, 16 Apr 2024 06:08:58 GMT, Serguei Spitsyn <sspit...@openjdk.org> wrote:
>> This is the test issue. The `WaitingPT3` thread posted the `MonitorWait` >> event but has not released the `lockCheck` monitor yet. It has been fixed to >> wait for each `WaitingTask` thread to really reach the `WAITING` state. The >> same approach is used for `EnteringTask` threads. It has been fixed to wait >> for each `EnteringTask` thread to reach the `BLOCKED_ON_MONITOR` state. >> >> Testing: >> - Reran the test >> `serviceability/jvmti/ObjectMonitorUsage/ObjectMonitorUsage.java` locally >> - TBD: submit the mach5 tiers 1-6 as well > > Serguei Spitsyn has updated the pull request incrementally with one > additional commit since the last revision: > > review: removed event_lock; moved wait_for_state() to jvmti_common.hpp Marked as reviewed by lmesnik (Reviewer). The fix looks good, just one nit. rml.wait(100); might be changed to plain sleep(100) ------------- PR Review: https://git.openjdk.org/jdk/pull/18778#pullrequestreview-2004437310 PR Comment: https://git.openjdk.org/jdk/pull/18778#issuecomment-2059776412
