I think runtime/logging/ItablesTest.java has a similar issue as JDK-8144953. The only occurrence of a "Resolving:" log output is in the interpreter runtime:

$ ack "Resolving:" hotspot/src/
hotspot/src/share/vm/interpreter/interpreterRuntime.cpp
768: log_develop_trace(itables)("Resolving: klass: %s to method: %s",

If class resolution happens in compiled code this test fails:

...
[0.354s][trace][itables] invokespecial resolved method: caller-class:<NULL>, compile-time-class:java.lang.ThreadGroup, method:java.lang.ThreadGroup.add(Ljava/lang/Thread;)V, method_holder:java.lang.ThreadGroup, access_flags:
[0.354s][trace][itables] invokespecial selected method: resolved-class:java.lang.ThreadGroup, compile-time-class:java.lang.ThreadGroup, method:java.lang.ThreadGroup.add(Ljava/lang/Thread;)V, method_holder:java.lang.ThreadGroup, access_flags:
];
 stderr: []
 exitValue = 0

java.lang.RuntimeException: 'Resolving: klass: ' missing from stdout/stderr

at jdk.test.lib.OutputAnalyzer.shouldContain(OutputAnalyzer.java:138)
at ItablesTest.main(ItablesTest.java:52)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:520)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:92)
at java.lang.Thread.run(Thread.java:804)