[GEODE-3755] DistributedTestRuleTest.shouldHaveFourDUnitVMsByDefault fails intermittently

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: tests
• Assignee: Kirk Lund
• Reporter: Kirk Lund
• Created: 05/Oct/17 17:29
• Updated: 20/Apr/18 19:52
• Resolved: 06/Oct/17 16:56

Description

DistributedTestRuleTest.shouldHaveFourDUnitVMsByDefault fails intermittently with:

org.apache.geode.test.dunit.rules.tests.DistributedTestRuleTest > shouldHaveFourDUnitVMsByDefault FAILED
    org.junit.ComparisonFailure: expected:<[4]> but was:<[5]>
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at org.apache.geode.test.dunit.rules.tests.DistributedTestRuleTest.shouldHaveFourDUnitVMsByDefault(DistributedTestRuleTest.java:35)

This occurs anytime DistributedTestRuleTest executes after one of the other dunit tests in geode-core that uses more than the default 4 dunit VMs. These include:

• LocatorDUnitTest.testMultipleLocatorsRestartingAtSameTime() <- uses 5 VMs in addition to controller & locator
• LocatorDUnitTest.testMultipleLocatorsRestartingAtSameTimeWithMissingServers() <- uses 5 VMs in addition to controller & locator
• PreferSerializedHARegionQueueTest.copyingHARegionQueueShouldNotThrowException() <- uses 7 VMs in addition to controller & locator

Issue Links

• is duplicated by: GEODE-3756 BeforeClassExampleTest.shouldHaveFourDUnitVMsByDefault fails intermittently