[prev in list] [next in list] [prev in thread] [next in thread]
List: openjdk-serviceability-dev
Subject: Integrated: 8328741: serviceability/jvmti/ObjectMonitorUsage/ObjectMonitorUsage.java failed with
From: Serguei Spitsyn <sspitsyn () openjdk ! org>
Date: 2024-04-24 9:04:33
Message-ID: X162RFpfH1U9_5Z7WJ2fVv1CQlQuYqOj03TsutSwPvg=.c326f4f2-1396-42ec-b6b5-ced2d599af65 () github ! com
[Download RAW message or body]
On Mon, 15 Apr 2024 06:47:24 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
This pull request has now been integrated.
Changeset: 174d6265
Author: Serguei Spitsyn <sspitsyn@openjdk.org>
URL: https://git.openjdk.org/jdk/commit/174d62652c69e811cf44ab64db575b13a848a728
Stats: 114 lines in 4 files changed: 20 ins; 80 del; 14 mod
8328741: serviceability/jvmti/ObjectMonitorUsage/ObjectMonitorUsage.java failed with \
unexpected owner
Reviewed-by: lmesnik, cjplummer
-------------
PR: https://git.openjdk.org/jdk/pull/18778
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic