From f62d301b9257542f5460902c400af3f947f10a66 Mon Sep 17 00:00:00 2001 From: Betsy McPhail Date: Tue, 9 Jun 2015 08:50:44 -0400 Subject: ctest: Optionally avoid starting tests that may exceed a given CPU load Add a TestLoad setting to CTest that can be set via a new --test-load command-line option, CTEST_TEST_LOAD variable, or TEST_LOAD option to the ctest_test command. Teach cmCTestMultiProcessHandler to measure the CPU load and avoid starting tests that may take more than the spare load currently available. The expression + <= must be true to start a new test. Co-Author: Zack Galbreath --- Modules/DartConfiguration.tcl.in | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'Modules/DartConfiguration.tcl.in') diff --git a/Modules/DartConfiguration.tcl.in b/Modules/DartConfiguration.tcl.in index 37a0a408ed..918b407bf6 100644 --- a/Modules/DartConfiguration.tcl.in +++ b/Modules/DartConfiguration.tcl.in @@ -95,6 +95,10 @@ SlurmRunCommand: @SLURM_SRUN_COMMAND@ # Currently set to 25 minutes TimeOut: @DART_TESTING_TIMEOUT@ +# During parallel testing CTest will not start a new test if doing +# so would cause the system load to exceed this value. +TestLoad: @CTEST_TEST_LOAD@ + UseLaunchers: @CTEST_USE_LAUNCHERS@ CurlOptions: @CTEST_CURL_OPTIONS@ # warning, if you add new options here that have to do with submit, -- cgit v1.2.1