The only way I could think that you could do this without making code modifications to ctest would be to run your whole test suite itself *as* a single test.
You could run it like this: ctest -R "^WholeTestSuite$" (which would run *just* the WholeTestSuite) And then the test for running WholeTestSuite would turn around and run: ctest -E "^WholeTestSuite$" (which would run all the tests *except* the WholeTestSuite) Then on the WholeTestSuite test, you could set a per-test timeout to whatever value makes sense (independent of the overall ctest timeout value). Or.... if you have time and ability, it should be fairly straightforward to make the appropriate modifications to ctest source code and submit it as a patch/feature-request to the bug tracker. HTH, David On Tue, Feb 3, 2009 at 4:34 AM, Bram de Greve <[email protected]>wrote: > Hello, > > Can anyone answer this question? > > I've tried the --test-timeout switch on ctest, but it seems to have no > effect. > > Thanks, > Bram > > > Hi, > > > > Is it possible to specify the total amount of time CTest may spend on > > running the tests? With CTEST_TIMEOUT, you can set the time CTest may > > spend on each test, but that's not really what I'm looking for. > > > > Thanks > > Bram > > _______________________________________________ > > CMake mailing list > > [email protected] > > http://www.cmake.org/mailman/listinfo/cmake > > > > > _______________________________________________ > CMake mailing list > [email protected] > http://www.cmake.org/mailman/listinfo/cmake >
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
