- 
    Bug 
- 
    Resolution: Fixed
- 
     P4 P4
- 
    18
- 
        b18
                    See https://github.com/openjdk/jdk/blob/8821b0004170e18c8e7d6e5bbe8759344ff769b1/test/lib/jdk/test/lib/cds/CDSOptions.java#L103
The test.cds.runtime.options property is used to execute the CDS tests in a special mode. E.g., create the archived with G1 but load the archive with EpsilonGC.
Currently tests that are launched with TestCommon.runWithArchive() and CDSTestUtils.runWithArchive() can handle -Dtest.cds.runtime.options. However, some test cases, such as dynamicArchive/HelloDynamic.java, do not call the above two methods, so they ignore -Dtest.cds.runtime.options.
The fix is to move the handling of -Dtest.cds.runtime.options to TestCommon.executeAndLog, because most CDS tests use this function to launch a child JVM.
            
The test.cds.runtime.options property is used to execute the CDS tests in a special mode. E.g., create the archived with G1 but load the archive with EpsilonGC.
Currently tests that are launched with TestCommon.runWithArchive() and CDSTestUtils.runWithArchive() can handle -Dtest.cds.runtime.options. However, some test cases, such as dynamicArchive/HelloDynamic.java, do not call the above two methods, so they ignore -Dtest.cds.runtime.options.
The fix is to move the handling of -Dtest.cds.runtime.options to TestCommon.executeAndLog, because most CDS tests use this function to launch a child JVM.
- relates to
- 
                    JDK-8270489 Support archived heap objects in EpsilonGC -           
- Resolved
 
-         
- 
                    JDK-8274033 Some tier-4 CDS EpsilonGC tests throw OOM -           
- Resolved
 
-         
 
        