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
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
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
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
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,
Hi,
I noticed that the automatic dependency graph generation in CMake targeting
GraphViz only considers targets of certain types. In particular, it only
adds nodes for executables and shared, static, and module libraries.
Is this deliberate?
If I submit a patch extending this functionality to
