+1 for this. I ended up having to parse the xml files myself, as I couldn't find an easier way to get the info I wanted.
I submitted a request for this.
http://public.kitware.com/Bug/view.php?id=8277

I was trying to use ctest as a replacement for a non-portable shell script that did nightly testing.

Clint

Floca Ralf Omar wrote:

Hello,

I want to use CTest for nightly builds. In this context I need to know if there were any errors while configuring, building or testing (…) the target. I need this to trigger other events in the nightly build script. (Platform: Windows XP, Visual Studio 2005)

When using CTest with the “–D Nightly” flag (or single step versions like NightlyUpdate), it seems that it returns an error value (!=0) if a step fails. This is true for all steps except the build step. Even if there is an error while building one of the target’s projects the return of CTest will be 0. In difference one failing test in the test step will cause a return value of != 0.

Is there any sound way to query if the build step failed or at least if any error occurred in the whole Nightly Build processing? It seems to me that parsing the build.xml file of the according nightly build for <Error> elements is not a very elegant way.

Thank you for any help or suggestion.

Kind regards,

Ralf Floca

------------------------------------------------------------------

Ralf Floca

DKFZ

German Cancer Research Center (Deutsches Krebsforschungszentrum)

Member of the Helmholtz Association

E071 Research Group

Software Development for Integrated Diagnostics and Therapy (SIDT)

Im Neuenheimer Feld 280

D-69120 Heidelberg

Telefon: +49 (6221) 42 3021

E-Mail: [EMAIL PROTECTED]

Web: www.dkfz.de

------------------------------------------------------------------

------------------------------------------------------------------------

_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake

_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to