From: <svn...@op...> - 2010-01-10 18:26:57
|
Author: scriptor Date: Sun Jan 10 19:26:47 2010 New Revision: 5995 URL: http://www.opensync.org/changeset/5995 Log: The timeouts were too long... And my current guess is, that it is CTestConfig.cmake only, that has effects on the test timeouts, in the end. So no need to set the timeouts in any of the CMakeLists.txt. Modified: plugins/ldap-sync/CTestConfig.cmake Modified: plugins/ldap-sync/CTestConfig.cmake ============================================================================== --- plugins/ldap-sync/CTestConfig.cmake Sun Jan 10 19:26:33 2010 (r5994) +++ plugins/ldap-sync/CTestConfig.cmake Sun Jan 10 19:26:47 2010 (r5995) @@ -1,7 +1,7 @@ ## This file should be placed in the root directory of your project. ## Then modify the CMakeLists.txt file in the root directory of your ## project to incorporate the testing dashboard. -## # The following are required to uses Dart and the Cdash dashboard +## # The following ones are required to use Dart and the Cdash dashboard ## ENABLE_TESTING() ## INCLUDE(Dart) set(CTEST_PROJECT_NAME "ldap-sync") @@ -20,9 +20,9 @@ # DART_TESTING_TIMEOUT must be set in CTestConfig.cmake rather than here. # At least, it seems so... IF (RUN_LONG_TESTS) - SET ( TIMEOUT 3600 CACHE STRING "General timeout value." FORCE ) + SET ( TIMEOUT 600 CACHE STRING "General timeout value." FORCE ) ELSE(RUN_LONG_TESTS) - SET ( TIMEOUT 480 CACHE STRING "General timeout value." FORCE ) + SET ( TIMEOUT 90 CACHE STRING "General timeout value." FORCE ) ENDIF(RUN_LONG_TESTS) SET ( CTEST_TEST_TIMEOUT ${TIMEOUT} CACHE STRING "The most natural variable for a timeout setting does NOT work. Great!" FORCE ) |