From 30e79bb4a388b59c5851b949a0dd559bc57e8ad3 Mon Sep 17 00:00:00 2001 From: Brad King Date: Mon, 4 Nov 2019 11:21:38 -0500 Subject: Tests: Extend RunCMake.CTestCommandLine internal timeout for valgrind A case added by commit 39ac8b4eb5 (ctest: Add --repeat-after-timeout option, 2019-10-29) includes a success-case timeout of 2 seconds. That is too short when running under valgrind, so extend it to 5 seconds. --- Tests/RunCMake/CTestCommandLine/repeat-after-timeout-cmake.cmake | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Tests/RunCMake/CTestCommandLine/repeat-after-timeout-cmake.cmake b/Tests/RunCMake/CTestCommandLine/repeat-after-timeout-cmake.cmake index 4dc9c36..873c0bd 100644 --- a/Tests/RunCMake/CTestCommandLine/repeat-after-timeout-cmake.cmake +++ b/Tests/RunCMake/CTestCommandLine/repeat-after-timeout-cmake.cmake @@ -9,7 +9,7 @@ add_test(NAME test1 COMMAND ${CMAKE_COMMAND} "-DTEST_OUTPUT_FILE=${TEST_OUTPUT_FILE}" -P "${CMAKE_CURRENT_SOURCE_DIR}/test1-timeout.cmake") -set_tests_properties(test1 PROPERTIES DEPENDS "initialization" TIMEOUT 2) +set_tests_properties(test1 PROPERTIES DEPENDS "initialization" TIMEOUT 5) add_test(hello ${CMAKE_COMMAND} -E echo hello) add_test(goodbye ${CMAKE_COMMAND} -E echo goodbye) -- cgit v0.12