MantisBT - CMake
View Issue Details
0011935CMakeCMakepublic2011-03-06 17:212015-07-08 08:57
Hassan 
Stephen Kelly 
normalminoralways
closedduplicate 
Visual Studio 9 2008Windows XP
CMake 2.8.3 
 
0011935: CTest with --output-on-failure option
We are using CMake with CTest and we found an issue regarding CTEST_OUTPUT_ON_FAILURE or –output-on-failure option in CTest.

I added:
set(CTEST_OUTPUT_ON_FAILURE ON)
command in out CMakeLists.txt file for enabling our PRINTF's and getting more details about the failed test(as mentioned in the book), but this is not working.
Currently for every CMake build we manually add this option in Visusal Studio setting and then it's working fine.
I also tried:
add_test(NAME ${TName} COMMAND ${TEST_NAME} ${TName} --output_on_failure) but it's also not working.
Is this the right way or I am missing some thing.
I am working on Windows XP and using Visual Studio 9 2008.
No tags attached.
duplicate of 0005977closed Bill Hoffman Add VERBOSE_TESTING setting for make runs of CTest 
Issue History
2011-03-06 17:21HassanNew Issue
2011-03-10 16:34Johan BjörkNote Added: 0025751
2011-03-10 16:34Johan BjörkNote Edited: 0025751bug_revision_view_page.php?bugnote_id=25751#r247
2012-08-11 21:35David ColeStatusnew => backlog
2012-08-11 21:35David ColeNote Added: 0030377
2015-02-26 15:25Stephen KellyRelationship addedduplicate of 0005977
2015-02-26 15:25Stephen KellyStatusbacklog => resolved
2015-02-26 15:25Stephen KellyResolutionopen => duplicate
2015-02-26 15:25Stephen KellyAssigned To => Stephen Kelly
2015-07-08 08:57Robert MaynardNote Added: 0039075
2015-07-08 08:57Robert MaynardStatusresolved => closed

Notes
(0025751)
Johan Björk   
2011-03-10 16:34   
It seems to be an *environment* variable, and not a variable. It works when I set it as an environment var, but I'd like to make it default without setting any variables.

(0030377)
David Cole   
2012-08-11 21:35   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0039075)
Robert Maynard   
2015-07-08 08:57   
Closing resolved issues that have not been updated in more than 4 months.