JDK-8230632 : [TESTBUG] appcds/NonExistClasspath.java and ClassPathAttr.java failed when running in hotspot_appcds_dynamic test group
  • Type: Bug
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: 14
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2019-09-04
  • Updated: 2019-09-26
  • Resolved: 2019-09-05
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 14
14 b14Fixed
Related Reports
Relates :  
It could be reproduced by specifying the following option with jtreg:

NonExistClasspath.java failed as follows:

patchJarForDynamicDump: classpath = foobar
result: Failed. Execution failed: `main' threw exception: java.lang.RuntimeException: FIXME: jar file not at a supported location

ClassPathAttr.java  timed out:

result: Error. Program `/scratch/ws/jdk14/build/linux-x64-debug/images/jdk/bin/java' timed out (timeout set to 120000ms, elapsed time including timeout handling was 124182ms).
URL: https://hg.openjdk.java.net/jdk/jdk/rev/06f3d5092832 User: ccheung Date: 2019-09-05 18:12:55 +0000

For the NonExistClasspath.java, a simple fix is just excluding the test from the hotspot_appcds_dynamic test group. For the ClassPathAttr.java, the timeout only reproducible if the test is run with the test group and on a linux host with many cores (32) and plenty of memory (~250GB). The timeout isn't reproducible after increasing the timeout value to 240.