You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2021/02/15 13:43:00 UTC
[jira] [Updated] (KUDU-3237)
MaintenanceManagerTest.TestCompletedOpsHistory is flaky
[ https://issues.apache.org/jira/browse/KUDU-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-3237:
------------------------------
Fix Version/s: (was: 1.15)
1.15.0
> MaintenanceManagerTest.TestCompletedOpsHistory is flaky
> -------------------------------------------------------
>
> Key: KUDU-3237
> URL: https://issues.apache.org/jira/browse/KUDU-3237
> Project: Kudu
> Issue Type: Test
> Reporter: Hao Hao
> Assignee: Alexey Serbin
> Priority: Major
> Fix For: 1.15.0
>
>
> Came across test failure in MaintenanceManagerTest.TestCompletedOpsHistory as the following:
> {noformat}
> I0125 19:55:10.782884 24454 maintenance_manager.cc:594] P 12345: op5 complete. Timing: real 0.000s user 0.000s sys 0.000s Metrics: {}
> /data/1/hao/Repositories/kudu/src/kudu/util/maintenance_manager-test.cc:525: Failure
> Expected: std::min(kHistorySize, i + 1)
> Which is: 6
> To be equal to: status_pb.completed_operations_size()
> Which is: 5
> I0125 19:55:10.783524 24420 test_util.cc:148] -----------------------------------------------
> I0125 19:55:10.783561 24420 test_util.cc:149] Had fatal failures, leaving test files at /tmp/dist-test-task1ofSWE/test-tmp/maintenance_manager-test.0.MaintenanceManagerTest.TestCompletedOpsHistory.1611604508702756-24420
> {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)