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 -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
