The IR Test Framework heavily uses getDeclaredClasses on the test class(es) which triggers class loading. That's a problem because some tests are carefully designed to not trigger loading of certain classes to exercise the (JIT) code handling unloaded classes.

One solution could be to use separate class loaders for separate @Test/@Run method invocations. This has the additional benefit of not polluting profiles and possibly making IR matching unstable depending on the order of test execution.