The test java/lang/management/MemoryMXBean/CollectionUsageThreshold.java fails when being run in nightly testing with various GC combinations:

Conflicting collector combinations in option list; please refer to the release notes for the combinations allowed

The problem is that the lists specific GC options in the "@run" tags. When Aurora runs baselines with different GC combinations, for example CMS, it will append the GC combination the "@run" tag. The result will be a run tag like the following:

 @run main/othervm/timeout=300 -XX:+PrintGCDetails -XX:+UseSerialGC -XX:+UseG1GC CollectionUsageThreshold

The test must either use ProcessTools to spawn new Java processes without passing along the options or check which GC it is being run with.