geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Darrel Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-128) Many expiration unit tests take too long to run on any type of PartitionedRegion
Date Thu, 16 Jul 2015 00:05:04 GMT

    [ https://issues.apache.org/jira/browse/GEODE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628976#comment-14628976
] 

Darrel Schneider commented on GEODE-128:
----------------------------------------

A pretty simple change to the testHook code sped these tests way up.
For example PartitionedRegionDUnitTest went from 5 minutes to 1 minute.


> 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
>   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)

Mime
View raw message