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

["Darrel Schneider (JIRA)" <ji...@apache.org>]

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

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

These tests set the LocalRegion.EXPIRY_MS_PROPERTY to cause expiration units to be milliseconds instead of seconds. For a non-PR the property only needs to be set when the region is created.

On a PR the property needs to be set when the bucket region is created. Simply moving the finally block that clears the sys prop down to the end of the test methods causes them to run much faster on a PR.


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