When jdk test java/lang/ClassLoader/GetPackage.java is run in Agent mode, it writes a bunch of tracing output to the stdout console stream, which is not captured as part of the test output.
 Here is sample output:

Passed: java/lang/ClassLoader/getResource/GetResource.sh
Passed: java/lang/ClassLoader/Assert.java
Passed: java/lang/ClassLoader/EndorsedDirs.java
Passed: java/lang/ClassLoader/ExceptionHidingLoader.java
Passed: java/lang/ClassLoader/ExtDirs.java
Passed: java/lang/ClassLoader/GetDotResource.java
Passed: java/lang/ClassLoader/GetPackage.java
Agent[0].stdout: package sun.reflect
Agent[0].stdout: package java.util
Agent[0].stdout: package sun.reflect.annotation
Agent[0].stdout: package java.lang.annotation
Agent[0].stdout: package java.nio
Agent[0].stdout: package java.security.cert
Agent[0].stdout: package java.util.zip
Agent[0].stdout: package sun.launcher
Agent[0].stdout: package sun.security.action
Agent[0].stdout: package java.nio.file
Agent[0].stdout: package java.nio.charset

Such output is very "alarming when watching the tests run locally/directly, as compared to running in a server-based batch environment where such output is typically not retained.

It would be better if the output were written to a stream that is captured, or the test run in othervm mode, which should also capture the output