JDK-8071910 : sun/tools/jmap/heapconfig/JMapHeapConfigTest.java fails on OS X and Solaris
  • Type: Bug
  • Component: hotspot
  • Sub-Component: svc
  • Affected Version: 9
  • Priority: P1
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2015-01-29
  • Updated: 2017-07-26
  • Resolved: 2015-02-12
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.
JDK 9
9Resolved
Related Reports
Cloners :  
JDK-8072013 - sun/tools/jmap/heapconfig/JMapHeapConfigTest.java fails on embedded platform
Duplicate :  
JDK-8072395 - sun/tools/jmap/heapconfig/LingeredAppTest.java and sun/tools/jmap/heapconfig/JMapHeapConfigTest.java fail due to LingeredApp ERROR: java.io.IOException: Lock is too old. Aborting
Relates :  
JDK-8072131 - sun/tools/jmap/heapconfig/JMapHeapConfigTest.java fails on mac
Relates :  
JDK-8072432 - JMapHeapConfigTest.java got java.io.IOException: Lock is too old
Description
sun/tools/jmap/heapconfig/JMapHeapConfigTest.java

This test was introduced in JDK-8042397, test fails on OS X and Solaris.

Starting jmap against 99584
----------System.err:(12/651)----------
java.lang.RuntimeException: Test FAILED jmap exits with non zero exit code 1
	at JMapHeapConfigTest.main(JMapHeapConfigTest.java:121)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at com.sun.javatest.regtest.MainAction$SameVMRunnable.run(MainAction.java:776)
	at java.lang.Thread.run(Thread.java:745)
Comments
So same problem as with all other SA based tests.
30-01-2015
You mean to print the output? It looks like TmtoolTestScenario.launch() is collecting the output in toolOutput, but when JMapHeapConfigTest.main detects that the exitcode is non-zero it does not print the toolOutput(). Even better would be to use ProcessTools in the testlibrary which handles this already.
30-01-2015
It would be a good improvement of the test if it printed the output from 'jmap' even when the exit value is non-zero.
30-01-2015