This is an automated email from the ASF dual-hosted git repository.

granthenke pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git


The following commit(s) were added to refs/heads/master by this push:
     new 9fa9239  [test] Set PROCESSORS to 4 for maintenance_mode-itest
9fa9239 is described below

commit 9fa923947c461325fafb28496903905413a58564
Author: Grant Henke <[email protected]>
AuthorDate: Wed Feb 10 10:50:04 2021 -0600

    [test] Set PROCESSORS to 4 for maintenance_mode-itest
    
    I saw frequent test failures when running maintenance_mode-itest
    in parallel on a 4 core machine. After running the example
    command below I identified that these heavy tests utilize 4 cores
    each and adjusted the PROCESSORS setting. With this change
    all the tests regularly pass.
    
    Command to identify PROCESSORS setting:
    perf stat -I1000 -e task-clock -o perf.txt 
../../thirdparty/installed/common/bin/ctest -R maintenance_mode-itest.4
    
    Change-Id: I89b479374266a64edf7fd455837c4d57a684694b
    Reviewed-on: http://gerrit.cloudera.org:8080/17055
    Reviewed-by: Alexey Serbin <[email protected]>
    Reviewed-by: Andrew Wong <[email protected]>
    Tested-by: Kudu Jenkins
---
 src/kudu/integration-tests/CMakeLists.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/kudu/integration-tests/CMakeLists.txt 
b/src/kudu/integration-tests/CMakeLists.txt
index 8ac1c3d..c4c8902 100644
--- a/src/kudu/integration-tests/CMakeLists.txt
+++ b/src/kudu/integration-tests/CMakeLists.txt
@@ -85,7 +85,7 @@ ADD_KUDU_TEST(fuzz-itest RUN_SERIAL true)
 ADD_KUDU_TEST(heavy-update-compaction-itest RUN_SERIAL true)
 ADD_KUDU_TEST(linked_list-test RUN_SERIAL true)
 ADD_KUDU_TEST(log-rolling-itest)
-ADD_KUDU_TEST(maintenance_mode-itest NUM_SHARDS 8
+ADD_KUDU_TEST(maintenance_mode-itest NUM_SHARDS 8 PROCESSORS 4
   DATA_FILES ../scripts/assign-location.py)
 ADD_KUDU_TEST(master_authz-itest RUN_SERIAL true NUM_SHARDS 8 PROCESSORS 4)
 ADD_KUDU_TEST(master_cert_authority-itest PROCESSORS 2)

Reply via email to