summaryrefslogtreecommitdiffstats
path: root/Tests/CTestTestTimeout
Commit message (Collapse)AuthorAgeFilesLines
* 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.
* Convert CMake-language commands to lower caseKitware Robot2012-08-132-27/+27
| | | | | | | | | | | | | | | | | 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.
* Longer CTestTestTimeout default time on CygwinBrad King2009-12-211-1/+5
| | | | | | | | | The commit "Make CTestTestTimeout time configurable" added a CMake cache variable CTestTestTimeout_TIME to configure the length of the timeout used by the inner CTestTestTimeout test. The reason was to allow users on slow machines to give this test some extra time without extending the timeout for everyone. However, Cygwin CMake seems to load slowly enough that it is worth a longer default timeout for that platform.
* Remove unnecessary configure time operations from CTestTest* testsZach Mullen2009-12-021-5/+0
|
* Make CTestTestTimeout time configurableBrad King2009-12-023-3/+9
| | | | | | | | | | | | | | | | In this test we start up a cmake script that runs a process that sleeps, and the timeout for the script is shorter than the sleep time. However, in order to properly detect that the sleeping grandchild is killed when the script times out we need to give sufficient time for the script to start the grandchild. Otherwise the log file for the grandchild is not available. On some (cygwin) builds our previous 1 second timeout for the script was not long enough to let the interpreter load and start the grandchild. We make the timeout time configurable by setting CTestTestTimeout_TIME in the cache for CMake itself. It tells the test how long to let the script run. The grandchild always sleeps for 4 seconds longer to ensure a comfortable window during which the process tree can be killed.
* Remove unused code from CTest test suiteBrad King2009-12-021-12/+1
| | | | | We remove from Tests/CTestTest*/CMakeLists.txt some historical cruft that is no longer used by the test suite.
* CTest: Test process tree kill on timeoutBrad King2009-11-304-2/+32
| | | | | | | | | | | We extend the CTestTestTimeout test to check that when a test times out its children (grandchildren of ctest) are killed. Instead of running the timeout executable directly, we run it through a cmake script that redirects the timeout executable output to a file. A second test later runs and verifies that the timeout executable was unable to complete and write data to the log file. Only if the first inner test times out and the second inner test passes (log is empty) does the CTestTestTimeout test pass.
* Improved safety and removed busy waiting from the CTestTestTimeout test.Zach Mullen2009-09-301-6/+11
|
* ENH: Added ctest test coverage for a test timeoutZach Mullen2009-09-294-0/+67