When there is a crash (as in libjava), the fatal error message output would be more helpful if it appeared in jtr files rather than only to standard out.
For example, this recent crash in libjava when running tests of build using latest linux devkits produces a jtr file with a standard failed communication error message, "Agent communication error: java.io.EOFException; check console log for any additional details" ,
http://java.se.oracle.com/mach5/view/9-dev-test/job/9-dev-tier1-linux-x64/2834/artifact/JTwork/jdk_test/java/nio/Buffer/Basic.jtr/*view*/
and the crash is only seen in standard out.
When run in jenkins, user must look in the console output, such as
http://java.se.oracle.com/mach5/view/9-dev-test/job/9-dev-tier1-linux-x64/2834/console to find this crash(below), which isn't always displayed near the test which created it (the ...'s are intervening out of other tests). This appears to be associated with ava/nio/Buffer/CopyDirectMemory.java, but goes with java/nio/Buffer/Basic.java. It must be rerun manually to really see this.
--------------------------------------------------
Agent[2].stdout: #
Agent[2].stdout: # A fatal error has been detected by the Java Runtime Environment:
Agent[2].stdout: #
Agent[2].stdout: # SIGSEGV (0xb) at pc=0x00007f7f115bf033, pid=23900, tid=5790
Agent[2].stdout: #
Agent[2].stdout: # JRE version: Java(TM) SE Runtime Environment (9.0-b139) (build 1.9.0-ea-b139)
Agent[2].stdout: # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.9.0-ea-b139, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Agent[2].stdout: # Problematic frame:
Agent[2].stdout: # C [libjava.so+0xd033] Java_java_nio_Bits_copyToShortArray+0x1f3
Agent[2].stdout: #
Agent[2].stdout: # Core dump will be written. Default location: Core dumps may be processed with "/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e" (or dumping to /scratch/jenkins/workspace/9-dev-tier1-linux-x64/JTwork/jdk_test/scratch/2/core.23900)
Agent[2].stdout: #
Agent[2].stdout: # An error report file with more information is saved as:
Agent[2].stdout: # /scratch/jenkins/workspace/9-dev-tier1-linux-x64/JTwork/jdk_test/scratch/2/hs_err_pid23900.log
Agent[2].stderr: Phoning home...
Agent[2].stderr: Using server: 10.161.186.18, port 4711
TEST: java/nio/Buffer/CopyDirectMemory.java
TEST RESULT: Passed. Execution successful
--------------------------------------------------
....
--------------------------------------------------
Agent[2].stdout: #
Agent[2].stdout: # If you would like to submit a bug report, please visit:
Agent[2].stdout: # http://bugreport.java.com/bugreport/crash.jsp
Agent[2].stdout: # The crash happened outside the Java Virtual Machine in native code.
Agent[2].stdout: # See problematic frame for where to report the bug.
Agent[2].stdout: #
TEST: java/lang/ClassLoader/Assert.java
TEST RESULT: Passed. Execution successful
--------------------------------------------------
...
--------------------------------------------------
Agent[2]: Exited, process exit code: 134
TEST: java/nio/Buffer/Basic.java
JDK under test: (build/jdk) . . .
For example, this recent crash in libjava when running tests of build using latest linux devkits produces a jtr file with a standard failed communication error message, "Agent communication error: java.io.EOFException; check console log for any additional details" ,
http://java.se.oracle.com/mach5/view/9-dev-test/job/9-dev-tier1-linux-x64/2834/artifact/JTwork/jdk_test/java/nio/Buffer/Basic.jtr/*view*/
and the crash is only seen in standard out.
When run in jenkins, user must look in the console output, such as
http://java.se.oracle.com/mach5/view/9-dev-test/job/9-dev-tier1-linux-x64/2834/console to find this crash(below), which isn't always displayed near the test which created it (the ...'s are intervening out of other tests). This appears to be associated with ava/nio/Buffer/CopyDirectMemory.java, but goes with java/nio/Buffer/Basic.java. It must be rerun manually to really see this.
--------------------------------------------------
Agent[2].stdout: #
Agent[2].stdout: # A fatal error has been detected by the Java Runtime Environment:
Agent[2].stdout: #
Agent[2].stdout: # SIGSEGV (0xb) at pc=0x00007f7f115bf033, pid=23900, tid=5790
Agent[2].stdout: #
Agent[2].stdout: # JRE version: Java(TM) SE Runtime Environment (9.0-b139) (build 1.9.0-ea-b139)
Agent[2].stdout: # Java VM: Java HotSpot(TM) 64-Bit Server VM (1.9.0-ea-b139, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Agent[2].stdout: # Problematic frame:
Agent[2].stdout: # C [libjava.so+0xd033] Java_java_nio_Bits_copyToShortArray+0x1f3
Agent[2].stdout: #
Agent[2].stdout: # Core dump will be written. Default location: Core dumps may be processed with "/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e" (or dumping to /scratch/jenkins/workspace/9-dev-tier1-linux-x64/JTwork/jdk_test/scratch/2/core.23900)
Agent[2].stdout: #
Agent[2].stdout: # An error report file with more information is saved as:
Agent[2].stdout: # /scratch/jenkins/workspace/9-dev-tier1-linux-x64/JTwork/jdk_test/scratch/2/hs_err_pid23900.log
Agent[2].stderr: Phoning home...
Agent[2].stderr: Using server: 10.161.186.18, port 4711
TEST: java/nio/Buffer/CopyDirectMemory.java
TEST RESULT: Passed. Execution successful
--------------------------------------------------
....
--------------------------------------------------
Agent[2].stdout: #
Agent[2].stdout: # If you would like to submit a bug report, please visit:
Agent[2].stdout: # http://bugreport.java.com/bugreport/crash.jsp
Agent[2].stdout: # The crash happened outside the Java Virtual Machine in native code.
Agent[2].stdout: # See problematic frame for where to report the bug.
Agent[2].stdout: #
TEST: java/lang/ClassLoader/Assert.java
TEST RESULT: Passed. Execution successful
--------------------------------------------------
...
--------------------------------------------------
Agent[2]: Exited, process exit code: 134
TEST: java/nio/Buffer/Basic.java
JDK under test: (build/jdk) . . .