-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
19
-
x86_64
-
os_x_10.15
The following test timed out in the JDK19 CI:
serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.java
Here's a snippet from the log file:
#section:driver
----------messages:(9/392)----------
command: driver JMapHProfLargeHeapTest
reason: User specified action: run driver JMapHProfLargeHeapTest
Mode: agentvm
Agent id: 11
Additional exports to unnamed modules from @modules: java.base/jdk.internal.misc java.management/sun.management jdk.internal.jvmstat/sun.jvmstat.monitor
Timeout refired 480 times
Timeout information:
--- Timeout information end.
elapsed time (seconds): 803.13
----------configuration:(19/2437)----------
<snip>
----------System.out:(4/2048)----------
STDOUT: /System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+15-879/macosx-x64-debug.jdk/jdk-19/fastdebug/bin/java: code object is not signed at all
Target JDK is not signed, therefore not hardened.
Command line: [/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+15-879/macosx-x64-debug.jdk/jdk-19/fastdebug/bin/java -cp /System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S41181/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/33956aad-3a7c-44d1-896b-ea2d39d53019/runs/8770fa24-bb63-451b-a467-985ccffae4ea/testoutput/test-support/jtreg_open_test_hotspot_jtreg_serviceability_sa/classes/3/serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.d:/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+15-879/src.full/open/test/hotspot/jtreg/serviceability/sa/jmap-hprof:/System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S41181/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/33956aad-3a7c-44d1-896b-ea2d39d53019/runs/8770fa24-bb63-451b-a467-985ccffae4ea/testoutput/test-support/jtreg_open_test_hotspot_jtreg_serviceability_sa/classes/3/test/lib:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/javatest.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/jtreg.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/junit.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/hamcrest.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/testng.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/jcommander.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/guice.jar --add-exports=java.management/sun.management=ALL-UNNAMED -Xmx1g JMapHProfLargeHeapProc 22528 ]
Extra
result: Error. Agent error: java.lang.Exception: Agent 11 timed out with a timeout of 480 seconds; check console log for any additional details
This timeout happened in a run with sightings of this bug:
JDK-8253074 SA tests time out on macOS after sudo due to runaway coresymbolicationd
However, there's no sign of a sudo cmd in the logs so I've filed
a new bug.
serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.java
Here's a snippet from the log file:
#section:driver
----------messages:(9/392)----------
command: driver JMapHProfLargeHeapTest
reason: User specified action: run driver JMapHProfLargeHeapTest
Mode: agentvm
Agent id: 11
Additional exports to unnamed modules from @modules: java.base/jdk.internal.misc java.management/sun.management jdk.internal.jvmstat/sun.jvmstat.monitor
Timeout refired 480 times
Timeout information:
--- Timeout information end.
elapsed time (seconds): 803.13
----------configuration:(19/2437)----------
<snip>
----------System.out:(4/2048)----------
STDOUT: /System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+15-879/macosx-x64-debug.jdk/jdk-19/fastdebug/bin/java: code object is not signed at all
Target JDK is not signed, therefore not hardened.
Command line: [/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+15-879/macosx-x64-debug.jdk/jdk-19/fastdebug/bin/java -cp /System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S41181/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/33956aad-3a7c-44d1-896b-ea2d39d53019/runs/8770fa24-bb63-451b-a467-985ccffae4ea/testoutput/test-support/jtreg_open_test_hotspot_jtreg_serviceability_sa/classes/3/serviceability/sa/jmap-hprof/JMapHProfLargeHeapTest.d:/System/Volumes/Data/mesos/work_dir/jib-master/install/jdk-19+15-879/src.full/open/test/hotspot/jtreg/serviceability/sa/jmap-hprof:/System/Volumes/Data/mesos/work_dir/slaves/c82600aa-2448-475c-8c08-6f02a5b3f3af-S41181/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/33956aad-3a7c-44d1-896b-ea2d39d53019/runs/8770fa24-bb63-451b-a467-985ccffae4ea/testoutput/test-support/jtreg_open_test_hotspot_jtreg_serviceability_sa/classes/3/test/lib:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/javatest.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/jtreg.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/junit.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/hamcrest.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/testng.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/jcommander.jar:/System/Volumes/Data/mesos/work_dir/jib-master/install/jtreg/6.1/1/bundles/jtreg-6.1+1.zip/jtreg/lib/guice.jar --add-exports=java.management/sun.management=ALL-UNNAMED -Xmx1g JMapHProfLargeHeapProc 22528 ]
Extra
result: Error. Agent error: java.lang.Exception: Agent 11 timed out with a timeout of 480 seconds; check console log for any additional details
This timeout happened in a run with sightings of this bug:
JDK-8253074 SA tests time out on macOS after sudo due to runaway coresymbolicationd
However, there's no sign of a sudo cmd in the logs so I've filed
a new bug.
- duplicates
-
JDK-8253074 SA tests time out on macOS after sudo due to runaway coresymbolicationd
- Open
- relates to
-
JDK-8253074 SA tests time out on macOS after sudo due to runaway coresymbolicationd
- Open