Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-17 Thread Ben Boeckel
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

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-17 Thread David Cole via cmake-developers
I agree with Brad, the --timeout command line parameter should only set/override the variable CTEST_TEST_TIMEOUT. The behavior w.r.t. test TIMEOUT properties should be left as is for this change. A **new** --timeout-scale with well defined / documented interactions with the global variable and

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-17 Thread Ben Boeckel
On Thu, Dec 17, 2015 at 13:54:08 -0500, David Cole wrote: > I agree with Brad, the --timeout command line parameter should only > set/override the variable CTEST_TEST_TIMEOUT. The behavior w.r.t. test > TIMEOUT properties should be left as is for this change. This behavior also makes sense to me.

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-17 Thread Alan W. Irwin
On 2015-12-17 13:54-0500 David Cole wrote: I agree with Brad, the --timeout command line parameter should only set/override the variable CTEST_TEST_TIMEOUT. The behavior w.r.t. test TIMEOUT properties should be left as is for this change. A **new** --timeout-scale with well defined /

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-17 Thread David Cole via cmake-developers
The principle "most local setting wins" should be followed. If a script is called without --timeout cmd line param, CTEST_TEST_TIMEOUT applies, if set. Otherwise default timeout value. If a script is called with --timeout cmd line param, then that **is** the timeout value, and

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-17 Thread David Cole via cmake-developers
Sounds to me like lapack should conditionally set CTEST_TEST_TIMEOUT only if it's not DEFINED already. With such code in the project, callers could define it on the command line with -D, or directly in a ctest -S script, and the passed in vale would "win" since in this case, the project would

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-15 Thread Ben Boeckel
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

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-15 Thread David Cole via cmake-developers
Thanks, Ben. That was gonna be my 2 cents, too: If I set a test property to have a 1, 5 or 10 second timeout, then I want the test to timeout if it takes any longer than that. I do this on tests which must execute quickly even in a loaded CPU scenario. I would not want the global timeout to take

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-15 Thread Alan W. Irwin
On 2015-12-15 13:53-0500 Ben Boeckel wrote: On Tue, Dec 15, 2015 at 10:33:38 -0800, Alan W. Irwin wrote: On 2015-12-15 11:20-0500 Ben Boeckel wrote: 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

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-15 Thread Ben Boeckel
On Tue, Dec 15, 2015 at 10:33:38 -0800, Alan W. Irwin wrote: > On 2015-12-15 11:20-0500 Ben Boeckel wrote: > > 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

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-15 Thread Alan W. Irwin
On 2015-12-15 11:20-0500 Ben Boeckel wrote: 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,

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-14 Thread Alan W. Irwin
On 2015-12-15 07:09+0100 Attila Krasznahorkay wrote: Hi Alan, Are you just looking for the TIMEOUT property on the tests? Hi Attila: No. As I said in my post, I tried that test property but the problem was that absolutely fixed the timeout for the test so it could not be overriden by the

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-14 Thread Attila Krasznahorkay
Hi Alan, Are you just looking for the TIMEOUT property on the tests? https://cmake.org/cmake/help/v3.0/command/set_tests_properties.html This is something that I managed to find with the most basic google-ing myself. :-/ And I use it like: set_tests_properties( ${testName}Test PROPERTIES

Re: [cmake-developers] [CMake] How to set _default_ timeout for the ctest command? (fwd)

2015-12-14 Thread Alan W. Irwin
I would appreciate it if a CMake developer who is familiar with the CTest timeout logic would answer my question below that was addressed to "@CMake developers:". Without such an answer (even if the conclusion is there is no way for an individual software package such as lapack to set a