Re: [cmake-developers] CTest script and many subprojects

Hi Zack, On 04/09/17 15:13, Zack Galbreath wrote: On Mon, Sep 4, 2017 at 7:50 AM, Wouter Klouwen > wrote: I think if I want it to work in the most optimal way where ctest can schedule all tests in the mega project for all

Re: [cmake-developers] CTest script and many subprojects

On Mon, Sep 4, 2017 at 7:50 AM, Wouter Klouwen wrote: > I think if I want it to work in the most optimal way where ctest can > schedule all tests in the mega project for all sub projects in > accordance with its load balancing, the SubProject attribute would have > to

Re: [cmake-developers] CTest script and many subprojects

Hi David, thanks for your view. I think if I want it to work in the most optimal way where ctest can schedule all tests in the mega project for all sub projects in accordance with its load balancing, the SubProject attribute would have to become a property of the test, instead of being a global

Re: [cmake-developers] CTest script and many subprojects

I think your analysis is correct. You could try doing a ctest_submit after each ctest_test call. Not sure if you could get "correct" results with that technique. I run some scripts that do something similar without subproject involved, and it mostly works, but messes up the +/- tests passed and

[cmake-developers] CTest script and many subprojects

Hi all, I've been having some success with CTest and am interested in using CDash as well. In order to generate some nice output, sub projects seem to be the best way of presenting the data in CDash for our setup. This setup is perhaps summed up by having one projects that contains a few