[
https://issues.apache.org/jira/browse/GEODE-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619548#comment-16619548
]
ASF subversion and git services commented on GEODE-5094:
--------------------------------------------------------
Commit b7df38854cbe8215b5c11ae0ae62eeec6394612c in geode's branch
refs/heads/feature/Micrometer from Dan Smith
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b7df388 ]
GEODE-5094: Replace flaky expiration with prexisting better one
ProxyJUnitTest.testExpiration used small timeouts and was flaky. It
looks like it was probably a near duplicate of a test that was already
refactored into RegionExpirationIntegrationTest. Removing the test and
parameterizing RegionExpirationIntegrationTest instead.
> ProxyJUnitTest fails intermittently in testExpiration
> -----------------------------------------------------
>
> Key: GEODE-5094
> URL: https://issues.apache.org/jira/browse/GEODE-5094
> Project: Geode
> Issue Type: Bug
> Components: expiration
> Reporter: Darrel Schneider
> Assignee: Dan Smith
> Priority: Major
> Labels: flaky, pull-request-available, swat
> Fix For: 1.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> {noformat}
> org.apache.geode.cache.ProxyJUnitTest > testExpiration FAILED
> org.apache.geode.cache.RegionDestroyedException:
> org.apache.geode.internal.cache.DistributedRegion[path='/rEMPTY';scope=DISTRIBUTED_NO_ACK';dataPolicy=EMPTY;
> concurrencyChecksEnabled]
> at
> org.apache.geode.internal.cache.LocalRegion.checkRegionDestroyed(LocalRegion.java:7391)
> at
> org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2723)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1356)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1314)
> at
> org.apache.geode.internal.cache.LocalRegion.get(LocalRegion.java:1299)
> at
> org.apache.geode.internal.cache.AbstractRegion.get(AbstractRegion.java:313)
> at
> org.apache.geode.cache.ProxyJUnitTest.testExpiration(ProxyJUnitTest.java:1106)
> {noformat}
> The test is scheduling a region to be destroyed if it is not used for 500
> miliseconds. It then starting doing gets which will keep using the region.
> But it is possible for the gets to lose the cpu and be prevented from using
> the region and it then expiring. That is what is happening in this test.
> This test as currently written is flaky and needs to be rewritten.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
