I found them (or some of them): 1) LocatorDUnitTest.testMultipleLocatorsRestartingAtSameTime() <- uses 5 VMs in addition to controller & locator 2) LocatorDUnitTest.testMultipleLocatorsRestartingAtSameTimeWithMissingServers() <- uses 5 VMs in addition to controller & locator 3) PreferSerializedHARegionQueueTest.copyingHARegionQueueShouldNotThrowException() <- uses 7 VMs in addition to controller & locator
I'll change the dunit infrastructure tests to get rid of any expectation of 4 default VMs since those tests may run after the above tests. Thanks, Kirk On Thu, Oct 5, 2017 at 10:05 AM, Kirk Lund <kl...@apache.org> wrote: > I need help looking for a geode-core dunit test that is using 5 dunit VMs > instead of 4. I want to review that test and then decide what to do with > the DistributedTest framework tests that might run after it (the tests that > verify that dunit itself is ok). > > This test is doing something like this: > > Host.getHost(0).getVM(4) <-- this is zero-based so it would cause dunit to > create a 5th VM > > Thanks, > Kirk >
