[
https://issues.apache.org/jira/browse/KUDU-3573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910381#comment-17910381
]
ASF subversion and git services commented on KUDU-3573:
-------------------------------------------------------
Commit fdfea715fe03f3032559302ecdfc5cee159480fb in kudu's branch
refs/heads/branch-1.18.x from Alexey Serbin
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=fdfea715f ]
KUDU-3573 fix flakiness in TestNewOpsDontGetScheduledDuringUnregister
Change-Id: Ie2b12be86f3a6ab52d8a0160b481e10b75054e15
Reviewed-on: http://gerrit.cloudera.org:8080/22248
Tested-by: Alexey Serbin <[email protected]>
Reviewed-by: Marton Greber <[email protected]>
Reviewed-by: Gabriella Lotz <[email protected]>
(cherry picked from commit 9a06aeb063c7d22143e853bcd95a64efa9a8f7f8)
Reviewed-on: http://gerrit.cloudera.org:8080/22303
Reviewed-by: Abhishek Chennaka <[email protected]>
> TestNewOpsDontGetScheduledDuringUnregister sometimes fail
> ---------------------------------------------------------
>
> Key: KUDU-3573
> URL: https://issues.apache.org/jira/browse/KUDU-3573
> Project: Kudu
> Issue Type: Sub-task
> Affects Versions: 1.17.0
> Reporter: Alexey Serbin
> Priority: Major
> Attachments: maintenance_manager-test.txt.xz
>
>
> The {{MaintenanceManagerTest.TestNewOpsDontGetScheduledDuringUnregister}}
> scenario fails from time to time with output like below:
> {noformat}
> src/kudu/util/maintenance_manager-test.cc:468: Failure
> Expected: (op1.DurationHistogram()->TotalCount()) <= (2), actual: 3 vs 2
> {noformat}
> Full output produced by the test scenario is attached.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
