JDK-8205532 : tests timeout intermittently on Solaris SPARC in "agentvm" mode
  • Type: Bug
  • Component: hotspot
  • Sub-Component: test
  • Affected Version: 11
  • Priority: P4
  • Status: Closed
  • Resolution: External
  • OS: solaris_11
  • CPU: sparc_64
  • Submitted: 2018-06-22
  • Updated: 2024-02-12
  • Resolved: 2018-11-09
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdResolved
Related Reports
Relates :  
JDK-8205526 - tests timeout intermittently in "agentvm" mode
Relates :  
JDK-8212628 - gc/arguments/TestSerialHeapSizeFlags.java failed with "Agent communication error: java.net.SocketException: Broken pipe (Write failed)"
Relates :  
JDK-8202975 - src/jdk/nashorn/internal/runtime/doubleconv/test/BignumTest.java failed with Agent communication error
Description
This bug is specific to Solaris SPARC so it is not a dup of:

    JDK-8205526 tests timeout intermittently in "agentvm" mode

During my analysis of jdk/jdk CI test failures, I'm seeing a
number of Solaris SPARC test timeouts that appear to be
caused by some failure in JTREG's "agentvm" mode.

This bug is intended as a gathering place for sightings of
test time outs on Solaris SPARC in "agentvm" mode only!
In particular, the JTREG test needs to fail with an error
message that looks like this:

test result: Error. Agent communication error: java.net.SocketTimeoutException: Read timed out; check console log for any additional details

and a timeout of about 3 minutes:

elapsed time (seconds): 180.008

Please DO NOT add sightings to this bug unless they are
Solaris SPARC hangs related to "agentvm" mode and they
timeout in about 3 minutes.
Comments
The issue is not reproduced with jtreg 4.2 b13. Closing this bug.
09-11-2018
I agree that we have not seen this specific failure mode for quite a while. Please feel free to close as "Cannot Reproduce".
09-11-2018
Added maintainer_pain label because most of these seem to be unrelated to any known product or test problem, but require effort to examine each such failure to decide whether it is "interesting".
22-10-2018
[~mikael] - why did you tag this one as 'testbug'?
28-06-2018
[~jjg] - Thanks for taking a look!
22-06-2018
I've found some (more) timeouts that are not scaled by timeoutFactor. I'll push a fix.
22-06-2018
[~dcubed] Noted
22-06-2018