[jira] [Commented] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

2018-09-18 Thread ASF subversion and git services (JIRA) 


[ 
https://issues.apache.org/jira/browse/GEODE-5094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

2018-09-14 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on GEODE-5094:


Commit b7df38854cbe8215b5c11ae0ae62eeec6394612c in geode's branch 
refs/heads/feature/GEODE-5729 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)

[jira] [Commented] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

2018-09-13 Thread ASF subversion and git services (JIRA) 


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

ASF subversion and git services commented on GEODE-5094:


Commit b7df38854cbe8215b5c11ae0ae62eeec6394612c in geode's branch 
refs/heads/develop 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)

[jira] [Commented] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

2018-09-07 Thread Dan Smith (JIRA) 


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

Dan Smith commented on GEODE-5094:
--

This test is still failing. Most recent failure:

https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/IntegrationTest/builds/355
{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:7418)
at 
org.apache.geode.internal.cache.LocalRegion.checkReadiness(LocalRegion.java:2757)
at 
org.apache.geode.internal.cache.LocalRegion.newUpdateEntryEvent(LocalRegion.java:1665)
at 
org.apache.geode.internal.cache.LocalRegion.put(LocalRegion.java:1625)
at 
org.apache.geode.internal.cache.AbstractRegion.put(AbstractRegion.java:413)  
at 
org.apache.geode.cache.ProxyJUnitTest.testExpiration(ProxyJUnitTest.java:1128)

{noformat}

> 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
>Priority: Major
>  Labels: flaky, swat
>
> {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)

[jira] [Commented] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

2018-04-20 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-5094:


Commit a03bba213a6b5932a9da9c0a4848c94fd485bbfb in geode's branch 
refs/heads/feature/transcoding_experiments from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a03bba2 ]

added flaky category to test method for GEODE-5094


> 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
>Priority: Major
>  Labels: flaky
>
> {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)

[jira] [Commented] (GEODE-5094) ProxyJUnitTest fails intermittently in testExpiration

2018-04-17 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on GEODE-5094:


Commit a03bba213a6b5932a9da9c0a4848c94fd485bbfb in geode's branch 
refs/heads/develop from [~dschneider]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=a03bba2 ]

added flaky category to test method for GEODE-5094


> 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
>Priority: Major
>  Labels: flaky
>
> {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)