The following test failed in the JDK17 CI:
serviceability/sa/ClhsdbPmap.java#id1
Here's a snippet from the log file:
#section:main
----------messages:(6/225)----------
command: main ClhsdbPmap true
reason: User specified action: run main/othervm/timeout=480 ClhsdbPmap true
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 4843.346
----------configuration:(0/0)----------
----------System.out:(11/1967)----------
Starting ClhsdbPmap test: withCore==true
Command line: ['/opt/mesos/jib-master/install/jdk-17+18-1443/macosx-x64-debug.jdk/jdk-17/fastdebug/bin/java' '-XX:MaxRAMPercentage=12' '-Djava.io.tmpdir=/opt/mesos/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S42436/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/07129351-9741-40d6-824a-09d9a09939b1/runs/182e553f-e6fc-4f2a-a6ea-d59b4cf1828e/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/tmp' '-XX:+CreateCoredumpOnCrash' '-XX:+UseZGC' '-XX:+CreateCoredumpOnCrash' '-Djava.library.path=/opt/mesos/jib-master/install/jdk-17+18-1443/macosx-x64-debug.test/hotspot/jtreg/native' '-cp' '/opt/mesos/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S42436/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/07129351-9741-40d6-824a-09d9a09939b1/runs/182e553f-e6fc-4f2a-a6ea-d59b4cf1828e/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/classes/1/serviceability/sa/ClhsdbPmap_id1.d:/opt/mesos/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S42436/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/07129351-9741-40d6-824a-09d9a09939b1/runs/182e553f-e6fc-4f2a-a6ea-d59b4cf1828e/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/classes/1/test/lib' 'jdk.test.lib.apps.LingeredApp' '91687f3a-32a0-4e78-9845-dfedec8f136e.lck' 'forceCrash']
[2021-04-11T00:48:38.281805Z] Gathering output for process 56976
[2021-04-11T00:48:38.433289Z] Waiting for completion for process 56976
[2021-04-11T00:48:38.433551Z] Waiting for completion finished for process 56976
Output and diagnostic info for process 56976 was saved into 'pid-56976-output.log'
[2021-04-11T00:48:38.454613Z] Waiting for completion for process 56976
[2021-04-11T00:48:38.454802Z] Waiting for completion finished for process 56976
Run test with ulimit -c: unlimited
Timeout refired 4800 times
LingeredApp failed to start: java.io.IOException: App waiting timeout
----------System.err:(20/1399)----------
java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Process is still alive. Can't get its output.
at ClhsdbPmap.main(ClhsdbPmap.java:88)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:831)
Caused by: java.lang.RuntimeException: Process is still alive. Can't get its output.
at jdk.test.lib.apps.LingeredApp.getOutput(LingeredApp.java:164)
at jdk.test.lib.apps.LingeredApp.finishApp(LingeredApp.java:376)
at jdk.test.lib.apps.LingeredApp.startAppExactJvmOpts(LingeredApp.java:426)
at jdk.test.lib.apps.LingeredApp.startApp(LingeredApp.java:440)
at ClhsdbPmap.main(ClhsdbPmap.java:63)
... 6 more
JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Process is still alive. Can't get its output.
JavaTest Message: shutting down test
STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Process is still alive. Can't get its output.
----------rerun:(37/6648)*----------
This is an odd failure. I did find the following old bug that also
mentioned "Process is still alive. Can't get its output.", but that
bug also has sightings of other failure modes so I didn't want
to reopen it:
JDK-8197591 Tests failing with App waiting timeout
serviceability/sa/ClhsdbPmap.java#id1
Here's a snippet from the log file:
#section:main
----------messages:(6/225)----------
command: main ClhsdbPmap true
reason: User specified action: run main/othervm/timeout=480 ClhsdbPmap true
Mode: othervm [/othervm specified]
Timeout information:
--- Timeout information end.
elapsed time (seconds): 4843.346
----------configuration:(0/0)----------
----------System.out:(11/1967)----------
Starting ClhsdbPmap test: withCore==true
Command line: ['/opt/mesos/jib-master/install/jdk-17+18-1443/macosx-x64-debug.jdk/jdk-17/fastdebug/bin/java' '-XX:MaxRAMPercentage=12' '-Djava.io.tmpdir=/opt/mesos/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S42436/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/07129351-9741-40d6-824a-09d9a09939b1/runs/182e553f-e6fc-4f2a-a6ea-d59b4cf1828e/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/tmp' '-XX:+CreateCoredumpOnCrash' '-XX:+UseZGC' '-XX:+CreateCoredumpOnCrash' '-Djava.library.path=/opt/mesos/jib-master/install/jdk-17+18-1443/macosx-x64-debug.test/hotspot/jtreg/native' '-cp' '/opt/mesos/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S42436/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/07129351-9741-40d6-824a-09d9a09939b1/runs/182e553f-e6fc-4f2a-a6ea-d59b4cf1828e/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/classes/1/serviceability/sa/ClhsdbPmap_id1.d:/opt/mesos/slaves/3c846bae-ce30-4a97-93ee-9fef4497ccb6-S42436/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/07129351-9741-40d6-824a-09d9a09939b1/runs/182e553f-e6fc-4f2a-a6ea-d59b4cf1828e/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_serviceability/classes/1/test/lib' 'jdk.test.lib.apps.LingeredApp' '91687f3a-32a0-4e78-9845-dfedec8f136e.lck' 'forceCrash']
[2021-04-11T00:48:38.281805Z] Gathering output for process 56976
[2021-04-11T00:48:38.433289Z] Waiting for completion for process 56976
[2021-04-11T00:48:38.433551Z] Waiting for completion finished for process 56976
Output and diagnostic info for process 56976 was saved into 'pid-56976-output.log'
[2021-04-11T00:48:38.454613Z] Waiting for completion for process 56976
[2021-04-11T00:48:38.454802Z] Waiting for completion finished for process 56976
Run test with ulimit -c: unlimited
Timeout refired 4800 times
LingeredApp failed to start: java.io.IOException: App waiting timeout
----------System.err:(20/1399)----------
java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Process is still alive. Can't get its output.
at ClhsdbPmap.main(ClhsdbPmap.java:88)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
at java.base/java.lang.Thread.run(Thread.java:831)
Caused by: java.lang.RuntimeException: Process is still alive. Can't get its output.
at jdk.test.lib.apps.LingeredApp.getOutput(LingeredApp.java:164)
at jdk.test.lib.apps.LingeredApp.finishApp(LingeredApp.java:376)
at jdk.test.lib.apps.LingeredApp.startAppExactJvmOpts(LingeredApp.java:426)
at jdk.test.lib.apps.LingeredApp.startApp(LingeredApp.java:440)
at ClhsdbPmap.main(ClhsdbPmap.java:63)
... 6 more
JavaTest Message: Test threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Process is still alive. Can't get its output.
JavaTest Message: shutting down test
STATUS:Failed.`main' threw exception: java.lang.RuntimeException: Test ERROR java.lang.RuntimeException: Process is still alive. Can't get its output.
----------rerun:(37/6648)*----------
This is an odd failure. I did find the following old bug that also
mentioned "Process is still alive. Can't get its output.", but that
bug also has sightings of other failure modes so I didn't want
to reopen it:
- relates to
-
JDK-8267433 Core dumps on OSX sometimes take a very long time
- Open
-
JDK-8253028 SA core file tests still time out on OSX with "java.io.IOException: App waiting timeout"
- Resolved
-
JDK-8268723 Problem list SA core file tests on OSX when using ZGC
- Resolved
-
JDK-8277345 investigate if specific failed tests are causing Mach5 task timeouts
- Closed
-
JDK-8197591 Tests failing with App waiting timeout
- Closed
-
JDK-8265350 SA tests time out on macOS 11.0
- Closed
(1 relates to)
There are no Sub-Tasks for this issue.