JDK-8252329 : runtime/LoadClass/TestResize.java timed out
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 16,18,19
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2020-08-25
  • Updated: 2022-07-14
  • Resolved: 2022-07-07
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 20
20 b06Fixed
Related Reports
Blocks :  
JDK-8184765 - Dynamically resize SystemDictionary
Description
The following test timed out in the JDK16 CI:

runtime/LoadClass/TestResize.java

Here's a snippet from the log file:

#section:driver
----------messages:(9/297)----------
command: driver TestResize
reason: User specified action: run driver TestResize 
Mode: agentvm
Agent id: 23
Additional exports to unnamed modules from @modules: java.base/jdk.internal.misc
Timeout refired 480 times
Timeout information:
--- Timeout information end.
elapsed time (seconds): 543.012
----------configuration:(14/1860)----------

<snip>

----------System.out:(8/1957)----------
Command line: [/scratch/opt/mach5/mesos/work_dir/jib-master/install/jdk-16+13-509/linux-aarch64-debug.jdk/jdk-16/fastdebug/bin/java -cp /scratch/opt/mach5/mesos/work_dir/slaves/1a7cca38-e299-473e-97af-f3151e5423d5-S71156/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/a7670255-4d8c-496e-8b40-59762c3058f9/runs/e3c2f726-ea93-4856-bc9d-59cf6756870b/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_runtime/classes/1/runtime/LoadClass/TestResize.d:/scratch/opt/mach5/mesos/work_dir/jib-master/install/jdk-16+13-509/src.full/open/test/hotspot/jtreg/runtime/LoadClass:/scratch/opt/mach5/mesos/work_dir/slaves/1a7cca38-e299-473e-97af-f3151e5423d5-S71156/frameworks/1735e8a2-a1db-478c-8104-60c8b0af87dd-0196/executors/a7670255-4d8c-496e-8b40-59762c3058f9/runs/e3c2f726-ea93-4856-bc9d-59cf6756870b/testoutput/test-support/jtreg_open_test_hotspot_jtreg_hotspot_runtime/classes/1/test/lib:/scratch/opt/mach5/mesos/work_dir/jib-master/install/jtreg/5.1/b01/bundles/jtreg_bin-5.1.zip/jtreg/lib/javatest.jar:/scratch/opt/mach5/mesos/work_dir/jib-master/install/jtreg/5.1/b01/bundles/jtreg_bin-5.1.zip/jtreg/lib/jtreg.jar:/scratch/opt/mach5/mesos/work_dir/jib-master/install/jtreg/5.1/b01/bundles/jtreg_bin-5.1.zip/jtreg/lib/junit.jar:/scratch/opt/mach5/mesos/work_dir/jib-master/install/jtreg/5.1/b01/bundles/jtreg_bin-5.1.zip/jtreg/lib/testng.jar -XX:+PrintSystemDictionaryAtExit -Xlog:safepoint+cleanup TriggerResize 50000 ]
[2020-08-25T18:34:28.982057325Z] Gathering output for process 15872
[2020-08-25T18:42:38.634437725Z] Waiting for completion for process 15872
[2020-08-25T18:42:38.634844050Z] Waiting for completion finished for process 15872
PASS table_size: 40423, classes: 50002, load factor: 1.2369690522722212 <= 5.0
PASS table_size: 107, classes: 0, load factor: 0.0 <= 5.0
PASS table_size: 1009, classes: 6, load factor: 0.005946481665014866 <= 5.0
PASS table_size: 1009, classes: 435, load factor: 0.4311199207135778 <= 5.0
----------System.err:(3/35)----------

JavaTest Message: Test complete.

result: Error. Agent error: java.lang.Exception: Agent 23 timed out with a timeout of 480 seconds; check console log for any additional details


test result: Error. Agent error: java.lang.Exception: Agent 23 timed out with a timeout of 480 seconds; check console log for any additional details
Comments
Changeset: f93beacd Author: Coleen Phillimore <coleenp@openjdk.org> Date: 2022-07-07 20:27:31 +0000 URL: https://git.openjdk.org/jdk/commit/f93beacd2f64aab0f930ac822859380c00c51f0c
07-07-2022
A pull request was submitted for review. URL: https://git.openjdk.org/jdk/pull/9394 Date: 2022-07-06 11:43:06 +0000
06-07-2022
I've attached the log for my jdk-19+29 stress test sighting on macosx-aarch64: $ unzip -l jdk-19+29_macosx-aarch64.8252329.zip Archive: jdk-19+29_macosx-aarch64.8252329.zip Length Date Time Name --------- ---------- ----- ---- 27882 07-02-2022 18:12 jdk-19+29_3/failures.macosx-aarch64/TestResize.jtr.slowdebug --------- ------- 27882 1 file
03-07-2022
The test runs a process that calls PrintSystemDictionaryAtExit, and then parses this large output with 50k classes. From the log file, the dictionary printout is complete so presumably the main process is still parsing the dictionary.
01-07-2022
I've attached the log for my jdk-19+27 stress test sighting on macosx-aarch64: $ unzip -l jdk-19+27_macosx-aarch64.8252329.zip Archive: jdk-19+27_macosx-aarch64.8252329.zip Length Date Time Name --------- ---------- ----- ---- 28018 06-18-2022 19:08 jdk-19+27_3/failures.macosx-aarch64/TestResize.jtr.slowdebug --------- ------- 28018 1 file
19-06-2022
Looking at recent JDK 17 CI test history the longest execution time has been seen on linux-aarch64 at 6m41s. The slowest macos-x64 is 4m57s. The 8 minute timeout should be more than ample. We would need to see the raw output to get some idea of whether the time is lost in running the actual resizing code, or in processing the output of the process.
06-07-2021
I just had this test timeout when running in GitHub Actions on macos-x64: PASS table_size: 20201, classes: 50002, load factor: 2.47522399881194 <= 5.0 PASS table_size: 1009, classes: 6, load factor: 0.005946481665014866 <= 5.0 PASS table_size: 107, classes: 0, load factor: 0.0 <= 5.0 PASS table_size: 1009, classes: 403, load factor: 0.3994053518334985 <= 5.0 TEST RESULT: Error. Agent error: java.lang.Exception: Agent 32 timed out with a timeout of 480 seconds; check console log for any additional details
06-07-2021
Try bumping up the timeout so that this is resolved.
11-01-2021
Taking it out of JDK16, but will keep it around to see if the issue continues to show up.
18-11-2020
I would take it out of JDK16 and keep an eye on whether it reproduces.
17-11-2020
Since it was just one time occurrence - should I spend my time on it, or take it out of JDK16 and hold on it for a bit to see if we get more?
17-11-2020
ILW = MLM = P4
01-09-2020