On Mon, Dec 14, 2015 at 23:01:31 -0800, Alan W. Irwin wrote:
> On the cmake general list, Brad recently answered my original query on this
> subject and appears to agree with me that that ctest --timeout
> option should always have the highest priority, i.e., override any
> timeout set by the project such as the above TIMEOUT property.
Here's the snippet from Brad's message:
> 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.
http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/54086/focus=54168
which implies that --timeout sets CTEST_TEST_TIMEOUT, but any properties
would ignore the setting (as they do now).
--Ben
--
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-developers
