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. If the > consensus continues to be that is the desired behaviour it appears > some CMake/CTest code changes will be necessary to change to that > behaviour.
Hmm. I don't know. Some tests have timeouts set because they either *do* take that long or *shouldn't* take as long as the timeout (e.g., those that might deadlock). I think, instead, that --min-timeout and --max-timeout options might be better which allow you to say "this machine is slow; tests may take longer (max(property, option))" or "this machine is fast, clamp down the timeout (min(property, option))". Alternatively, a --timeout-scale option to multiply all timeouts in properties might be better. --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
