This test fails on an AArch64 system (not necessarily unique to this platform, however) while looking for the line "waiting to re-lock in wait" in reference to the object java/lang/ref/ReferenceQueue$Lock.
This line never appears in the output and instead it seems the object referred to has the line "waiting to lock" associated with it instead.
The way the test is currently written there is not a straightforward way to tell the test to look for "waiting to lock" in reference to java/lang/ref/ReferenceQueue$Lock, as it finds "waiting to lock" in reference to java/lang/Class first.
This line never appears in the output and instead it seems the object referred to has the line "waiting to lock" associated with it instead.
The way the test is currently written there is not a straightforward way to tell the test to look for "waiting to lock" in reference to java/lang/ref/ReferenceQueue$Lock, as it finds "waiting to lock" in reference to java/lang/Class first.
- relates to
-
JDK-8192985 SA: Test cases for the clhsdb 'inspect', 'scanoops' and 'printas' commands
-
- Resolved
-