geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk Lund (JIRA)" <>
Subject [jira] [Created] (GEODE-3755) DistributedTestRuleTest.shouldHaveFourDUnitVMsByDefault fails intermittently
Date Thu, 05 Oct 2017 17:30:01 GMT
Kirk Lund created GEODE-3755:

             Summary: DistributedTestRuleTest.shouldHaveFourDUnitVMsByDefault fails intermittently
                 Key: GEODE-3755
             Project: Geode
          Issue Type: Bug
          Components: tests
            Reporter: Kirk Lund

DistributedTestRuleTest.shouldHaveFourDUnitVMsByDefault fails intermittently with:
org.apache.geode.test.dunit.rules.tests.DistributedTestRuleTest > shouldHaveFourDUnitVMsByDefault
    org.junit.ComparisonFailure: expected:<[4]> but was:<[5]>
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
        at org.apache.geode.test.dunit.rules.tests.DistributedTestRuleTest.shouldHaveFourDUnitVMsByDefault(
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

This message was sent by Atlassian JIRA

View raw message