[jira] [Updated] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky

2018-10-29 Thread Ryan McMahon (JIRA)


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

Ryan McMahon updated GEODE-5568:

Issue Type: Bug  (was: Test)

> testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
> -
>
> Key: GEODE-5568
> URL: https://issues.apache.org/jira/browse/GEODE-5568
> Project: Geode
>  Issue Type: Bug
>  Components: tests
>Reporter: Michael Oleske
>Assignee: Bill
>Priority: Major
>  Labels: pull-request-available, swat
>  Time Spent: 5h 20m
>  Remaining Estimate: 0h
>
> *We* should remove flakiness from test
> *Before* we add more features around Query Monitor
> *Because* flaky tests do not inspire confidence
> *Notes*
> When running [PR 2311|https://github.com/apache/geode/pull/2311], a test 
> failed that passed on a rerun (see 
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel])
> The build artifacts are available 
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz]
> Since it is a timing issue, it could be a few things so not sure on best path 
> forward.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky

2018-10-11 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot updated GEODE-5568:
--
Labels: pull-request-available swat  (was: swat)

> testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
> -
>
> Key: GEODE-5568
> URL: https://issues.apache.org/jira/browse/GEODE-5568
> Project: Geode
>  Issue Type: Test
>  Components: tests
>Reporter: Michael Oleske
>Assignee: Bill
>Priority: Major
>  Labels: pull-request-available, swat
>
> *We* should remove flakiness from test
> *Before* we add more features around Query Monitor
> *Because* flaky tests do not inspire confidence
> *Notes*
> When running [PR 2311|https://github.com/apache/geode/pull/2311], a test 
> failed that passed on a rerun (see 
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel])
> The build artifacts are available 
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz]
> Since it is a timing issue, it could be a few things so not sure on best path 
> forward.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky

2018-10-02 Thread Bill (JIRA)


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

Bill updated GEODE-5568:

Labels: swat  (was: )

> testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
> -
>
> Key: GEODE-5568
> URL: https://issues.apache.org/jira/browse/GEODE-5568
> Project: Geode
>  Issue Type: Test
>  Components: tests
>Reporter: Michael Oleske
>Priority: Major
>  Labels: swat
>
> *We* should remove flakiness from test
> *Before* we add more features around Query Monitor
> *Because* flaky tests do not inspire confidence
> *Notes*
> When running [PR 2311|https://github.com/apache/geode/pull/2311], a test 
> failed that passed on a rerun (see 
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel])
> The build artifacts are available 
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz]
> Since it is a timing issue, it could be a few things so not sure on best path 
> forward.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (GEODE-5568) testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky

2018-08-14 Thread Michael Oleske (JIRA)


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

Michael Oleske updated GEODE-5568:
--
Component/s: tests

> testCacheOpAfterQueryCancel in QueryMonitorDUnitTest is potentially flaky
> -
>
> Key: GEODE-5568
> URL: https://issues.apache.org/jira/browse/GEODE-5568
> Project: Geode
>  Issue Type: Test
>  Components: tests
>Reporter: Michael Oleske
>Priority: Major
>
> *We* should remove flakiness from test
> *Before* we add more features around Query Monitor
> *Because* flaky tests do not inspire confidence
> *Notes*
> When running [PR 2311|https://github.com/apache/geode/pull/2311], a test 
> failed that passed on a rerun (see 
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-results/distributedTest/1534096152/classes/org.apache.geode.cache.query.dunit.QueryMonitorDUnitTest.html#testCacheOpAfterQueryCancel])
> The build artifacts are available 
> [here|http://files.apachegeode-ci.info/builds/geode-pr-2311/test-artifacts/1534096152/distributedtestfiles-geode-pr-2311.tgz]
> Since it is a timing issue, it could be a few things so not sure on best path 
> forward.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)