The test hotspot/test/serviceability/sa/TestPrintMdo.java is supposed to be executed only with server VMs and if the emulated client configuration is not enabled. At least the statement at the beginning of the tests seems to indicate that:

@requires vm.flavor == "server" & !vm.emulatedClient

While RBT-testing my planned change for JDK-8175340, I've come across the TestPrintMdo.java test failed with the following message:

----------System.err:(17/1528)----------
java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: One or more of 'VirtualCallData', 'CounterData', 'ReceiverTypeData', 'bci', 'MethodData' or 'java/lang/Object' not found
at TestPrintMdo.verifyPrintMdoOutput(TestPrintMdo.java:100)
at TestPrintMdo.main(TestPrintMdo.java:171)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:547)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:110)
at java.base/java.lang.Thread.run(Thread.java:844)
Caused by: java.lang.RuntimeException: One or more of 'VirtualCallData', 'CounterData', 'ReceiverTypeData', 'bci', 'MethodData' or 'java/lang/Object' not found
at TestPrintMdo.verifyPrintMdoOutput(TestPrintMdo.java:94)
... 7 more

The VM version was:

java version "9-internal"
Java(TM) SE Runtime Environment (fastdebug build 9-internal+0-2017-02-23-163851.zmajo.8175340)
Java HotSpot(TM) Server VM (fastdebug build 9-internal+0-2017-02-23-163851.zmajo.8175340, mixed mode, emulated-client)

That seems to indicate that the test is indeed executed in the emulated client configuration (which probably should not be).