This is an automated email from the ASF dual-hosted git repository. alexey pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/kudu.git
commit 4ab2e7564619b80555a8ddc60a9162cffe75084e Author: Alexey Serbin <[email protected]> AuthorDate: Tue Dec 3 21:58:51 2019 -0800 [test] KUDU-2610 fix flakiness in kudu-admin-test scenario I saw AdminCliTest.TestSimultaneousLeaderTransferAndAbruptStepdown failing with timed-out error trying to write data to the test table: http://dist-test.cloudera.org/job?job_id=aserbin.1575418627.126650 A log from another occurrence of this issue is attached to https://issues.apache.org/jira/browse/KUDU-2610 It seems the frequency of the leader change/step-down requests might be safely decreased to make this test more stable. The test already have the frequency of the leader change requests clamped down for ASAN builds compared with the RELEASE/DEBUG/TSAN case. Change-Id: I98e792783efa2909d10174f84ddd785f5a968046 Reviewed-on: http://gerrit.cloudera.org:8080/14827 Reviewed-by: Adar Dembo <[email protected]> Tested-by: Kudu Jenkins --- src/kudu/tools/kudu-admin-test.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/kudu/tools/kudu-admin-test.cc b/src/kudu/tools/kudu-admin-test.cc index 6670975..6d8f3c6 100644 --- a/src/kudu/tools/kudu-admin-test.cc +++ b/src/kudu/tools/kudu-admin-test.cc @@ -1507,9 +1507,9 @@ TEST_F(AdminCliTest, TestSimultaneousLeaderTransferAndAbruptStepdown) { // complete, so we'll back off on how frequently we disrupt leadership to give // time for progress to be made. #if defined(ADDRESS_SANITIZER) - const auto leader_change_period_sec = MonoDelta::FromMilliseconds(5000); + const auto leader_change_period_sec = MonoDelta::FromMilliseconds(6000); #else - const auto leader_change_period_sec = MonoDelta::FromMilliseconds(1000); + const auto leader_change_period_sec = MonoDelta::FromMilliseconds(2000); #endif const string& master_addr = cluster_->master()->bound_rpc_addr().ToString();
