[lilliput-jdk17u:lilliput] RFR: 8307764: [Lilliput/JDK17] Fix JVMTI GetObjectMonitorUsage()

[Roman Kennke]

On Tue, 9 May 2023 15:58:40 GMT, Roman Kennke <rkennke at openjdk.org> wrote:

> This test:
> make run-test TEST=vmTestbase/nsk/jvmti/GetObjectMonitorUsage/objmonusage001/TestDescription.java
> 
> fails with:
> (0) unexpected owner: Thread-1 (0x(nil))
> (0) waiter_count expected: 1, actually: 0
> 
> Reason is that [JDK-8295849](https://bugs.openjdk.org/browse/JDK-8295849) (which is a pre-req for Lilliput) has not been backported properly.
> 
> A number of other JVMTI tests are failing because of the same issue, too:
> 
> vmTestbase/nsk/jvmti/GetObjectMonitorUsage/objmonusage001/TestDescription.java
> vmTestbase/nsk/jvmti/GetObjectMonitorUsage/objmonusage003/TestDescription.java
> vmTestbase/nsk/jvmti/GetObjectMonitorUsage/objmonusage004/TestDescription.java
> vmTestbase/nsk/jvmti/scenarios/contention/TC01/tc01t001/TestDescription.java
> vmTestbase/nsk/jvmti/scenarios/contention/TC03/tc03t001/TestDescription.java
> vmTestbase/nsk/jvmti/scenarios/contention/TC03/tc03t002/TestDescription.java
> 
> Testing:
>  - [x] all failing tests (see above)
>  - [x] all of vmTestbase/nsk/jvmti
>  - [x] all of serviceability/jvmti

Thanks!

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

PR Comment: https://git.openjdk.org/lilliput-jdk17u/pull/15#issuecomment-1540531026