JDK-8180260 : Test plan for JDK-8179302 - Pre-resolve constant pool string entries and cache resolved_reference arrays in CDS archive
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: runtime
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2017-05-11
  • Updated: 2017-07-11
  • Resolved: 2017-07-11
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 10
10Resolved
Description
+ New test development:

[1] Different VM configuration parameters (GC type, etc) -- ensure graceful failure when G1 is not ensured, etc. Test all combinations that are incompatible with new feature.
[2] Can still use archive even when cache heap object regions cannot be mapped into Java heap.
[3] No crash after class redefinition (run several GC cycles)
[4] Ensure compatibility with shared classes loaded by custom class loaders => white box method to query ConstantPool::_resolved_references oop. This can also be sued to check that the array is populated corrected with archived strings.
   
+ Updates to test definition: any changes needed to the test definitions?

N.A.

+ Test execution: what kind of test execution is needed before pushing?
[1] Stress tests like WLS + AppCDS
[2] kitchensink + Bootstrap CDS
[3] All GC tests in bootstrap CDS mode
[4] Regular tier2~5