JDK-8019361 : [TESTBUG] Conflicting collector combinations in option list for GC tests
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs24,hs25,7u40,7u65,emb-8u26,8,9
  • Priority: P2
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-06-28
  • Updated: 2017-07-26
  • Resolved: 2014-11-20
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 9
9Fixed
Related Reports
Blocks :  
Duplicate :  
Relates :  
Relates :  
Sub Tasks
JDK-8062536 :  
JDK-8062537 :  
JDK-8062926 :  
Comments
The below test fail in two different ways either the normal way where both the test and the runner specify a GC: Conflicting collector combinations in option list; please refer to the release notes for the combinations allowed Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. Or a new way caused by ResourceManagement, which requires G1 and therefore can't be run with any other collector: ResourceManagement is only supported with the G1 collector (UseG1GC) Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit. RULE closed/gc/resource/TestAccuracyLevel.java ExitCode 1 RULE closed/gc/resource/TestAfterConcMarkCycle.java ExitCode 1 RULE closed/gc/resource/TestAfterFullGC.java ExitCode 1 RULE closed/gc/resource/TestAfterYoungGC.java ExitCode 1 RULE closed/gc/resource/TestContextChange.java ExitCode 1 RULE closed/gc/resource/TestInternedStrings.java ExitCode 1 RULE closed/gc/resource/TestOutOfMemory.java ExitCode 1 RULE closed/gc/resource/TestReusedDestroyedContext.java ExitCode 1 RULE closed/gc/resource/TestVerifyContexts.java ExitCode 1 RULE closed/serviceability/resource/TestContextIdLimit.java ExitCode 1 RULE closed/serviceability/resource/TestContextReuse.java ExitCode 1 RULE closed/serviceability/resource/TestCreateUntilFull.java ExitCode 1 RULE closed/serviceability/resource/TestDestroyInvalid.java ExitCode 1 RULE closed/serviceability/resource/TestDestroyTwice.java ExitCode 1 RULE closed/serviceability/resource/TestDestroyWhileUsed.java ExitCode 1 RULE closed/serviceability/resource/TestLifecycle.java ExitCode 1 RULE closed/serviceability/resource/TestLifecycleCurrThread.java ExitCode 1 RULE closed/serviceability/resource/TestRaceCreateDestroy.java ExitCode 1 RULE closed/serviceability/resource/TestSetContextDestroyed.java ExitCode 1 RULE closed/serviceability/resource/TestSetContextInvalid.java ExitCode 1 RULE closed/serviceability/resource/TestSetThreadInvalid.java ExitCode 1 RULE closed/serviceability/resource/TestThreadInherit.java ExitCode 1
18-09-2014

Created JDK-8055111 bug to handle the Utils.removeGcOpts bug.
14-08-2014

One of the bugs is that -Xconcgc isn't filtered out in: jdk9/jdk/test/lib/testlibrary/jdk/testlibrary/Utils.java: /** * Removes any options specifying which GC to use, for example "-XX:+UseG1GC". * Removes any options matching: -XX:(+/-)Use*GC * Used when a test need to set its own GC version. Then any * GC specified by the framework must first be removed. * @return A copy of given opts with all GC options removed. */ private static final Pattern useGcPattern = Pattern.compile("\\-XX\\:[\\+\\-]Use.+GC"); public static List<String> removeGcOpts(List<String> opts) { List<String> optsWithoutGC = new ArrayList<String>(); for (String opt : opts) { if (useGcPattern.matcher(opt).matches()) { System.out.println("removeGcOpts: removed " + opt); } else { optsWithoutGC.add(opt); } } return optsWithoutGC; } I think this change needs some more tweaks: changeset: 9766:e0c909934cd6 user: mtobiass date: Wed Apr 16 12:40:19 2014 -0700 summary: 8030628: Update java/lang/management/MemoryMXBean tests to ignore GC setting by jtreg
14-08-2014

RULE java/lang/management/MemoryMXBean/ResetPeakMemoryUsage.java Exception java.lang.RuntimeException: Expected to get exit value of [0]
22-07-2014

RULE gc/6581734/Test6581734.java ExitCode 1
22-07-2014

ILW=HMM I=H: false negative failures on all levels of testing L=H: nightly/pit/adhoc/promotion testing are affected always W=M: it is possible to use jtreg groups however it is needed to change ALL SQE testing (VM/STT/Embedded)
15-07-2014

nightly embedded: http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=313877.JAVASE_EMBEDDED_NIGHTLY-51 RULE gc/TestSystemGC.java ExitCode 1 RULE gc/8000311/Test8000311.java ExitCode 1 RULE gc/TestG1ZeroPGCTJcmdThreadPrint.java ExitCode 1 RULE gc/arguments/TestAlignmentToUseLargePages.java ExitCode 1 RULE gc/g1/TestRegionAlignment.java ExitCode 1 RULE gc/g1/TestShrinkToOneRegion.java ExitCode 1 RULE gc/metaspace/G1AddMetaspaceDependency.java ExitCode 1 RULE gc/metaspace/TestMetaspacePerfCounters.java ExitCode 1 RULE gc/metaspace/TestPerfCountersAndMemoryPools.java ExitCode 1
07-11-2013

There's an ongoing discussion on how this should be solved. It's unclear at this point if this should be addressed by the test harness or if the tests themselves need to change and in that case how. Waiting for the discussion to settle before we address this bug. Other bugs caused by the same issue (like JDK-8024111) are P4s so I'm lowering this bug to P4 as well.
26-09-2013

Other gc tests affected as well. RULE gc/arguments/TestAlignmentToUseLargePages.java ExitCode 1 RULE gc/metaspace/TestPerfCountersAndMemoryPools.java ExitCode 1 Run details page: http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=292760.JAVASE.PIT.VM-77#JT_HS%20%5B!jfr%5D%20(jtreg)_gc/arguments/TestAlignmentToUseLargePages.java http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=292760.JAVASE.PIT.VM-81#JT_HS%20%5B!jfr%5D%20(jtreg)_gc/arguments/TestAlignmentToUseLargePages.java http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=292760.JAVASE.PIT.VM-7#JT_HS%20%5B!jfr%5D%20(jtreg)_gc/arguments/TestAlignmentToUseLargePages.java http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=292760.JAVASE.PIT.VM-202#JT_HS%20%5B!jfr%5D%20(jtreg)_gc/arguments/TestAlignmentToUseLargePages.java http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=292760.JAVASE.PIT.VM-271#JT_HS%20%5B!jfr%5D%20(jtreg)_gc/arguments/TestAlignmentToUseLargePages.java http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=292760.JAVASE.PIT.VM-406#JT_HS%20%5B!jfr%5D%20(jtreg)_gc/arguments/TestAlignmentToUseLargePages.java http://aurora.ru.oracle.com/functional/faces/RunDetails.xhtml?names=292760.JAVASE.PIT.VM-332#JT_HS%20%5B!jfr%5D%20(jtreg)_gc/arguments/TestAlignmentToUseLargePages.java
24-09-2013

RULE gc/g1/TestShrinkToOneRegion.java ExitCode 1
10-07-2013