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.
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 :
|
Description
It could be reproduced by specifying the following option with jtreg:
-vmoptions:-Dtest.dynamic.cds.archive=true
NonExistClasspath.java failed as follows:
----------System.out:(1/43)----------
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).
Comments
|