Thanks Jens! I was searching for the cause on Friday but couldn't find it. Looks like any static usage of ClusterStartupRule ends up launching DUnit VMs. Gradle JUnit class loads (but does not instantiate) *Test.java. The tests that have public static ClusterStartupRules result in ClusterStartupRule being instantiated and the constructor contains "DUnitLauncher.launchIfNeeded();" so we're launching DUnit VMs in both the UnitTest and IntegrationTest targets.
I'm going to assign GEODE-4885 to myself and try to move "DUnitLauncher.launchIfNeeded();" from the constructor to the before on ClusterStartupRule. On Sun, Mar 18, 2018 at 3:02 PM, Jens Deppe <jensde...@apache.org> wrote: > It appears that DistributedRestoreSystemPropertiesTest is intermittently > failing and breaking the build. > > My initial analysis shows that the use of *categories* results in *all* > test classes being instantiated and some of those instantiations end up > launching DUnit VMs as a result of static or parameterized declarations. > This results in a false/positive situation > causing DistributedRestoreSystemPropertiesTest to fail intermittently. > > I think I've pinpointed the classes causing the situation and listed them > in the Jira. https://issues.apache.org/jira/browse/GEODE-4885. > > For now I've disabled the test to get builds going again. > > --Jens >
