[ 
https://issues.apache.org/jira/browse/GEODE-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Hanson resolved GEODE-5418.
--------------------------------
    Resolution: Fixed

This bug was addressed by GEODE-3451 which was a big refactor of this whole 
space of tests.

> Many flaky tests in children of MultiVMRegionTestCase
> -----------------------------------------------------
>
>                 Key: GEODE-5418
>                 URL: https://issues.apache.org/jira/browse/GEODE-5418
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Patrick Rhomberg
>            Priority: Major
>         Attachments: DistributedTest_metrics.txt
>
>
> When running DIstributedTest 200+ times, we observed that this group of tests 
> has many methods that are flaky
> {noformat}
> org.apache.geode.cache30.DiskDistributedNoAckAsyncOverflowRegionDUnitTest.testDistributedRegionDestroy:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DiskDistributedNoAckSyncOverflowRegionDUnitTest.testEntryIdleDestroy:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedAckOverflowRegionCCEOffHeapDUnitTest.testClearWithConcurrentEventsAsync:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedAckOverflowRegionCCEOffHeapDUnitTest.testConcurrentEventsOnNonReplicatedRegion:
>   2 failures (99.11894273127754% success rate)
> org.apache.geode.cache30.DistributedAckPersistentRegionCCEDUnitTest.testClearWithConcurrentEvents:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedAckPersistentRegionCCEOffHeapDUnitTest.testInvalidateEntry:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedAckPersistentRegionCCEOffHeapDUnitTest.testNBRegionDestructionDuringGetInitialImage:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedAckPersistentRegionCCEOffHeapDUnitTest.testNetSearchObservesIdleTime:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedAckPersistentRegionCCEOffHeapDUnitTest.testNonblockingGetInitialImage:
>   2 failures (99.11894273127754% success rate)
> org.apache.geode.cache30.DistributedAckPersistentRegionCCEOffHeapDUnitTest.testTombstones:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionCCEDUnitTest.testEntryIdleDestroy:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionCCEDUnitTest.testTXMultiRegion:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionCCEDUnitTest.testTXRmtMirror:  
> 3 failures (98.6784140969163% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionCCEOffHeapDUnitTest.testConcurrentEventsOnNonReplicatedRegion:
>   2 failures (99.11894273127754% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionCCEOffHeapDUnitTest.testRegionIdleInvalidate:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionCCEOffHeapDUnitTest.testTXRmtMirror:
>   3 failures (98.6784140969163% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionCCEOffHeapDUnitTest.testTombstones:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionDUnitTest.testTXRmtMirror:  5 
> failures (97.79735682819384% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest.testMirroredLocalLoad:
>   1 failures (99.55947136563876% success rate)
> org.apache.geode.cache30.DistributedNoAckRegionOffHeapDUnitTest.testTXRmtMirror:
>   8 failures (96.47577092511013% success rate)
> org.apache.geode.cache30.PartitionedRegionOffHeapDUnitTest.testDistributedUpdate:
>   7 failures (96.91629955947137% success rate)
> {noformat}
> Whoever picks this up can split these out if they are not related, but 
> leaving them as a single ticket here in case they have a common cause.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to