[ 
https://issues.apache.org/jira/browse/KUDU-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305734#comment-17305734
 ] 

Bankim Bhavsar commented on KUDU-3266:
--------------------------------------

Fix: https://gerrit.cloudera.org/c/17211/

> Flakiness in dynamic_multi_master_test in VerifyClusterAfterMasterAddition() 
> function
> -------------------------------------------------------------------------------------
>
>                 Key: KUDU-3266
>                 URL: https://issues.apache.org/jira/browse/KUDU-3266
>             Project: Kudu
>          Issue Type: Test
>          Components: master, test
>    Affects Versions: 1.15.0
>            Reporter: Bankim Bhavsar
>            Assignee: Bankim Bhavsar
>            Priority: Major
>
> {noformat}
> ParameterizedRecoverMasterTest.TestRecoverDeadMasterSysCatalogCopy/1: 
> /data0/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/integration-tests/cluster_verifier.cc:119:
>  Failure
> Failed
> Bad status: Not found: Unable to open table: the table does not exist: 
> table_name: "table-1"
> /data0/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/master/dynamic_multi_master-test.cc:603:
>  Failure
> Expected: cv.CheckRowCount(table_name, ClusterVerifier::EXACTLY, 0) doesn't 
> generate new fatal failures in the current thread.
>   Actual: it does.
> 2021-03-17T17:04:19Z chronyd exiting
> /data0/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/master/dynamic_multi_master-test.cc:1099:
>  Failure
> Expected: VerifyClusterAfterMasterAddition(master_hps, orig_num_masters_) 
> doesn't generate new fatal failures in the current thread.
>   Actual: it does.
> {noformat}
> Although the same verification function is used by other tests for add 
> master, this flakiness started showing up after introduction of the 
> RecoverDeadMaster test.
> https://github.com/apache/kudu/commit/4b4a8c0f2fdfd15524510821b27fc9c3b5d26b6b



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to