On 12/09/2015 10:06 PM, Alan W. Irwin wrote: > Also, the documentation of the ctest --timeout option says: > > `--timeout <seconds>` > Set a global timeout on all tests. > > This option will set a global timeout on all tests that do not > already have a timeout set on them.
Yes, one can see that implemented here: https://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/CTest/cmCTestTestHandler.cxx;hb=v3.4.1#l1112 https://cmake.org/gitweb?p=cmake.git;a=blob;f=Source/cmCTest.cxx#l2108 Here is a commit that set the order of precedence: Local test timeouts will now always take precedence over the global --timeout option. https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=c32088cf >From the history of that code it looks like --timeout was added with no consideration of its relationship to CTEST_TEST_TIMEOUT. Some other CTest options in the same scope as CTEST_TEST_TIMEOUT can be overridden by the command line, so I agree that --timeout should override it too. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
