[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Re: RFR: 8328741: serviceability/jvmti/ObjectMonitorUsage/ObjectMonitorUsage.java failed with
From:       Serguei Spitsyn <sspitsyn () openjdk ! org>
Date:       2024-04-24 9:04:32
Message-ID: TG2ytRbKJE3BblNFKiqO31lCDebpvQP_eLIQVGUPS08=.a4c58d94-0258-4b89-92d2-1588ceae1d77 () github ! com
[Download RAW message or body]

On Wed, 24 Apr 2024 00:01:45 GMT, Serguei Spitsyn <sspitsyn@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: rename ensureWaitsToBeNotified to ensureWaitingToBeNotified

Thank you for review, Leonid and Chris!

-------------

PR Comment: https://git.openjdk.org/jdk/pull/18778#issuecomment-2074450724


[prev in list] [next in list] [prev in thread] [next in thread]