summaryrefslogtreecommitdiffstats
path: root/Tests/RunCMake/ctest_test/RunCMakeTest.cmake
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'backport-ctest-repeat-notrun' into ctest-repeat-notrunBrad King2020-05-271-6/+32
|\
| * CTest: Make sure NOT_RUN tests show up in the failed test logRobert Maynard2020-05-271-1/+11
| | | | | | | | Issue: #20543
| * Tests: Add coverage of ctest_test RETURN_VALUE and REPEATRobert Maynard2020-05-271-5/+21
| |
* | CTest: Log environment variables as a test measurementKyle Edwards2020-05-191-0/+11
| |
* | ctest: add option --stop-on-failureJohnny Jazeix2020-04-201-0/+12
|/ | | | | | To stop the tests once one has failed Fixes: #16628
* ctest_test: Add option to REPEAT testsBrad King2019-11-071-1/+21
|
* CTest: Fix --test-load regressionBrad King2018-09-101-4/+4
| | | | | | | | | | | | | | | | | | | | | | | The `ctest --test-load` option is implemented in `StartNextTests` by not starting any tests when the load is too high and instead sleeping and then returning. Prior to commit v3.11.0-rc1~117^2 (CTest: Re-implement test process handling using libuv, 2017-12-10) our outer loop in `RunTests` would immediately call `StartNextTests` again. However, now the `uv_run` loop may simply terminate if there are no tests running because no events are left pending. Fix this by converting the sleep in `StartNextTests` into a libuv timer that it starts instead. This avoids leaving `uv_run` with no pending events. In the case that there are other running tests this also allows CTest to detect when they finish even if it during the wait period where we previously slept. This regression was not caught by the test suite because it only verified that we do not start new tests when the load was too high and not that we proceed to start tests when the load drops. Revise the test suite to cover both. Fixes: #18338
* Tests: Disable parallel test execution while running ctest_testStephen Kelly2015-10-271-0/+1
|
* CTest: Document and test custom output size settingsBrad King2015-09-181-0/+15
| | | | | | | | | Add documentation and tests for the existing CTEST_CUSTOM_MAXIMUM_PASSED_TEST_OUTPUT_SIZE CTEST_CUSTOM_MAXIMUM_FAILED_TEST_OUTPUT_SIZE CTest variables.
* CTest: Optionally add a ChangeId attribute on XML Site tagsZack Galbreath2015-07-171-0/+10
| | | | | | | Add variable CTEST_CHANGE_ID to configure the setting. This allows CTest clients to give CDash information about what change is being tested so that CDash can take actions to report the results (e.g. to a pull request page).
* ctest: Optionally avoid starting tests that may exceed a given CPU loadBetsy McPhail2015-06-301-0/+41
| | | | | | | | | | | | | | 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 <current_load> + <test_processors> <= <max-load> must be true to start a new test. Co-Author: Zack Galbreath <zack.galbreath@kitware.com>
* ctest_test: Add QUIET optionZack Galbreath2015-02-231-0/+10
generated by cgit v0.12 at 2024-11-15 06:45:07 (GMT)