Sometimes like in bug JDK-8212628 jtreg reports:
test result: Error. Agent communication error: java.net.SocketException: Broken pipe (Write failed); check console log for any additional details
While test failed with JVM crash. See more details in bugJDK-8212628.
The issue is not only that message is confusing and hide exact test result. There are not any artifacts generated/preserved. So there is no any way to investigated test failures.
I filed this bug separately fromCODETOOLS-7902346 because it describes a significantly more complex issue. The fix for CODETOOLS-7902346 might just update message.
test result: Error. Agent communication error: java.net.SocketException: Broken pipe (Write failed); check console log for any additional details
While test failed with JVM crash. See more details in bug
The issue is not only that message is confusing and hide exact test result. There are not any artifacts generated/preserved. So there is no any way to investigated test failures.
I filed this bug separately from
- relates to
-
CODETOOLS-7903082 test failed with "Error. Agent communication error: java.io.EOFException"
-
- New
-
-
CODETOOLS-7902346 Need better message when test times out in agentvm mode
-
- Resolved
-
-
JDK-8212628 gc/arguments/TestSerialHeapSizeFlags.java failed with "Agent communication error: java.net.SocketException: Broken pipe (Write failed)"
-
- Closed
-