Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
BeforeClassExampleTest.shouldHaveFourDUnitVMsByDefault fails intermittently with:
org.apache.geode.test.dunit.examples.BeforeClassExampleTest > 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.examples.BeforeClassExampleTest.shouldHaveFourDUnitVMsByDefault(BeforeClassExampleTest.java:37)
This occurs anytime BeforeClassExampleTest 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
Attachments
Issue Links
- duplicates
-
GEODE-3755 DistributedTestRuleTest.shouldHaveFourDUnitVMsByDefault fails intermittently
- Closed