You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2016/01/08 05:41:43 UTC

[jira] [Updated] (GEODE-128) Many expiration unit tests take too long to run on any type of PartitionedRegion

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

Anthony Baker updated GEODE-128:
--------------------------------
    Fix Version/s: 1.0.0-alpha1

> Many expiration unit tests take too long to run on any type of PartitionedRegion
> --------------------------------------------------------------------------------
>
>                 Key: GEODE-128
>                 URL: https://issues.apache.org/jira/browse/GEODE-128
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Darrel Schneider
>            Assignee: Darrel Schneider
>            Priority: Minor
>             Fix For: 1.0.0-alpha1
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Here are some of the unit tests I noticed are taking too long to run:testCustomEntryIdleTimeout1	40 sec	Passed
> testCustomEntryIdleTimeout2	40 sec	Passed
> testCustomEntryTtl2	40 sec	Passed
> testEntryExpirationAfterMutate	40 sec	Passed
> testExtendedKeysValues	33 sec	Passed
> testCustomEntryTtl1	20 sec	Passed
> testEntryTtlInvalidate	20 sec	Passed
> These are all on PartitionedRegionDUnitTest. For non PR regions I see these same test methods only take 200ms.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)