David Holmes

But if one test has a problem and messes up the debugger won't that kill the rest of the tests?

I agree there is a more general issue of test interference in anything other than `othervm` mode but that is beside the point. It seems to me that going from...

Hi Julian, Given the JEP was closed/rejected as being unnecessary it didn't really make sense to present this as an Implementation of the JEP. This is simply the last couple...

@OssamaLouati thanks for the work you have put into doing this upgrade of the tests. That said I do have a fewconcerns about this change, but let me start by...

> Every log (as any Finalazible object) is registered using registerCleanup() But you have changed Log so it is no longer a FinalizableObject. ?? Ah I see this is what...

> Note we can't check if the current thread owns a lock without grabbing dbgRawMonitor. In fact the main purpose of dbgRawMonitor is to allow the current thread to check...

> Unfortunately checking ownership means comparing jobjects, which you can't safely do if you are comparing to a jobject that could be freed at any moment Okay but how does...

The modified tests are failing in our CI on Linux x64 and Aarch64 - see https://bugs.openjdk.org/browse/JDK-8335643

> class checks inspired by hotspot/share/classfile/classFileParser.cpp Just to be clear any such checks are mandated by the JVMS

@asotona pardon my ignorance of the Classfile API usage, but I had thought that the API could be used to either write the bytecode representation of class, or else introspect...