[CMake] cdash/ctest question

Biddiscombe, John A. biddisco at cscs.ch
Tue Jan 19 02:55:27 EST 2016


Alex

Thank you for this information. I shall test this out right away.

Yours

JB

-----Original Message-----
From: Alexander Neundorf [mailto:a.neundorf-work at gmx.net] 
Sent: 14 January 2016 23:17
To: cmake at cmake.org
Cc: Biddiscombe, John A.
Subject: Re: [CMake] cdash/ctest question

On Thursday, January 14, 2016 21:51:23 Biddiscombe, John A. wrote:
> Apologies for posting a cdash question question to the cmake list…
> 
> CDash plots the run-time of tests, which is very useful indeed, but it 
> would be even more useful if one could output a performance related 
> ‘time’ from a test where a specific feature was being benchmarked and 
> one could see how it changes over a period of days/weeks/months as 
> changes to code are being made.
> The time would be specific to the tested code and not include startup 
> and other uninteresting overheads (such as when the filesystem is 
> misbehaving and the test starts slowly).
> Does such a feature exist in ctest/cdash at all?

yes, we do exactly that.

You have to generate <DartMeasurement> tags in the stdoutof the test <DartMeasurement name="Simple" type="numeric/integer">42</DartMeasurement>
<DartMeasurement name="ExecutionTime" 
type="numeric/double">1.23456</DartMeasurement>

and then in cdash you can configure the tests-overview page to display certain such measurements by name, and on the tests page you can also display graphs for such named measurements.

Alex




More information about the CMake mailing list