summaryrefslogtreecommitdiffstats
path: root/Tests/CTestTestScheduler
Commit message (Collapse)AuthorAgeFilesLines
* Tests: Drop CMAKE_TEST_GENERATOR(|_TOOLSET) variablesBrad King2014-03-031-2/+2
| | | | s/CMAKE_TEST_GENERATOR/CMAKE_GENERATOR/g
* CTestTest*: Update minimum required CMake to 2.4Brad King2013-10-231-1/+1
| | | | We will soon deprecate support for compatibility with CMake < 2.4.
* Tests: Add generator toolset supportBrad King2013-02-071-0/+1
| | | | | Propagate CMAKE_GENERATOR_TOOLSET through the test hierarchy so that all tests can build with the selected generator toolset, if any.
* Remove CMake-language block-end command argumentsKitware Robot2012-08-132-2/+2
| | | | | | | | | | | | | | | | | Ancient versions of CMake required else(), endif(), and similar block termination commands to have arguments matching the command starting the block. This is no longer the preferred style. Run the following shell code: for c in else endif endforeach endfunction endmacro endwhile; do echo 's/\b'"$c"'\(\s*\)(.\+)/'"$c"'\1()/' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | egrep -z -v 'Tests/CMakeTests/While-Endwhile-' | xargs -0 sed -i -f convert.sed && rm convert.sed
* Convert CMake-language commands to lower caseKitware Robot2012-08-132-21/+21
| | | | | | | | | | | | | | | | | Ancient CMake versions required upper-case commands. Later command names became case-insensitive. Now the preferred style is lower-case. Run the following shell code: cmake --help-command-list | grep -v "cmake version" | while read c; do echo 's/\b'"$(echo $c | tr '[:lower:]' '[:upper:]')"'\(\s*\)(/'"$c"'\1(/g' done >convert.sed && git ls-files -z -- bootstrap '*.cmake' '*.cmake.in' '*CMakeLists.txt' | egrep -z -v '^(Utilities/cm|Source/kwsys/)' | xargs -0 sed -i -f convert.sed && rm convert.sed
* Tests: Eliminate unnecessary files and variables.David Cole2011-01-281-3/+0
| | | | | | | | | | | | | | | | | | | | | 1: The CTestTestFailedSubmits tests do not need to run the CTEST_MEMCHECK command. It is covered by the CTestTest2 test. If more coverage *is* required, choose a test that runs by itself once to add it to... This one gets used several times in a loop to test submission failure via the various submission protocols. With memchecking on, each test here takes 1000 seconds or more on a "fast" build... 2: Other ctest tests do not need any of the CTEST_MEMORYCHECK_* variables defined. They don't even call CTEST_MEMCHECK, or -D NightlyMemCheck, or anything. So: remove the unnecessary set calls. 3: CTestTest3 has gone intentionally unused for months because it did not add any coverage and caused no ends of sporadic randomish failures when network connectivity was spotty. Remove its directory. Never add it again.
* Fix CTestTestScheduler sporadic failure.Zach Mullen2010-05-072-4/+4
| | | | Increased the time difference between each test so that overburdened systems won't fail this test sometimes.
* Add unit test to ensure that CTestCostData scheduling works correctlyZach Mullen2010-02-034-0/+68