Re: [CMake] ctest/cdash question

2014-09-06 Thread Biddiscombe, John A.
David Of course. So simple, I just tried it and it works, that will save me a lot of script tweaking. Thanks very much JB On 06/09/14 03:18, David Cole dlrd...@aol.com wrote: Not off topic at all. Try start, test, submit, test, submit. Should work. Start is the thing that writes a new

Re: [CMake] ctest/cdash question

2014-09-06 Thread David Cole via CMake
You're welcome. One caveat to mention with this sort of submit pattern (submitting multiple build or test chunks to a single row on the CDash dashboard) is that it messes up the incremental +n/-n compare-to-previous-submission numbers of build warnings and errors, and number of test passes

Re: [CMake] ctest/cdash question

2014-09-06 Thread Biddiscombe, John A.
David OK, understood. Currently, the buildbot is running 145 unit tests, then 52 regression tests in separate steps, every dashboard line has +145 and -52 respectively so the +/- numbers can’t get much worse! My dashboard is 1.8.2 which dates back a few years. Just seeing the red/green (and one

[CMake] ctest/cdash question

2014-09-05 Thread Biddiscombe, John A.
Sorry if this is off topic for the list. If I ctest –D ExperimentalStart ctest –D ExperimentalTest –R test1 ctest –D ExperimentalSubmit Then ctest –D ExperimentalStart ctest –D ExperimentalTest –R test2 ctest –D ExperimentalSubmit It appears as two entries on the dashboard, but I’d like to have

Re: [CMake] ctest/cdash question

2014-09-05 Thread David Cole via CMake
Not off topic at all. Try start, test, submit, test, submit. Should work. Start is the thing that writes a new time stamp tag, and all that follows should be associated with the most recent start's tag. HTH, David C. On Sep 5, 2014, at 5:07 PM, Biddiscombe, John A. biddi...@cscs.ch wrote: