summaryrefslogtreecommitdiffstats
path: root/Help/command
diff options
context:
space:
mode:
authorBrad King <brad.king@kitware.com>2019-11-15 14:16:50 (GMT)
committerKitware Robot <kwrobot@kitware.com>2019-11-15 14:17:26 (GMT)
commitc1ae0532f3a1d6d2c7b6e8f370be2a6dca89bf93 (patch)
tree56b7e8550dd4836e5fbb63d3a6bb14a3eef190fe /Help/command
parentaba3048055be13b168b08537d877bbfaab28c978 (diff)
parent28994115e83b568ccba546db26a55381cbad244d (diff)
downloadCMake-c1ae0532f3a1d6d2c7b6e8f370be2a6dca89bf93.zip
CMake-c1ae0532f3a1d6d2c7b6e8f370be2a6dca89bf93.tar.gz
CMake-c1ae0532f3a1d6d2c7b6e8f370be2a6dca89bf93.tar.bz2
Merge topic 'ctest_test-repeat'
28994115e8 ctest_test: Add option to REPEAT tests 42d5d8f425 cmCTestMultiProcessHandler: Hold repeat mode as a member ed65b3e984 CTest: Rename internal APIs for --repeat options Acked-by: Kitware Robot <kwrobot@kitware.com> Merge-request: !4011
Diffstat (limited to 'Help/command')
-rw-r--r--Help/command/ctest_test.rst20
1 files changed, 20 insertions, 0 deletions
diff --git a/Help/command/ctest_test.rst b/Help/command/ctest_test.rst
index 7a3393b..5c67b2c 100644
--- a/Help/command/ctest_test.rst
+++ b/Help/command/ctest_test.rst
@@ -23,6 +23,7 @@ Perform the :ref:`CTest Test Step` as a :ref:`Dashboard Client`.
[STOP_TIME <time-of-day>]
[RETURN_VALUE <result-var>]
[CAPTURE_CMAKE_ERROR <result-var>]
+ [REPEAT <mode>:<n>]
[QUIET]
)
@@ -95,6 +96,25 @@ The options are:
and then the ``--test-load`` command-line argument to :manual:`ctest(1)`.
See also the ``TestLoad`` setting in the :ref:`CTest Test Step`.
+``REPEAT <mode>:<n>``
+ Run tests repeatedly based on the given ``<mode>`` up to ``<n>`` times.
+ The modes are:
+
+ ``UNTIL_FAIL``
+ Require each test to run ``<n>`` times without failing in order to pass.
+ This is useful in finding sporadic failures in test cases.
+
+ ``UNTIL_PASS``
+ Allow each test to run up to ``<n>`` times in order to pass.
+ Repeats tests if they fail for any reason.
+ This is useful in tolerating sporadic failures in test cases.
+
+ ``AFTER_TIMEOUT``
+ Allow each test to run up to ``<n>`` times in order to pass.
+ Repeats tests only if they timeout.
+ This is useful in tolerating sporadic timeouts in test cases
+ on busy machines.
+
``SCHEDULE_RANDOM <ON|OFF>``
Launch tests in a random order. This may be useful for detecting
implicit test dependencies.