[cmake-developers] [CMake 0015557]: CTest misses build errors if launchers enabled in CTest but not in CMake

Mantis Bug Tracker mantis at public.kitware.com
Wed May 6 12:57:38 EDT 2015


The following issue has been SUBMITTED. 
====================================================================== 
http://www.cmake.org/Bug/view.php?id=15557 
====================================================================== 
Reported By:                trsystran
Assigned To:                
====================================================================== 
Project:                    CMake
Issue ID:                   15557
Category:                   CTest
Reproducibility:            have not tried
Severity:                   minor
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2015-05-06 12:57 EDT
Last Modified:              2015-05-06 12:57 EDT
====================================================================== 
Summary:                    CTest misses build errors if launchers enabled in
CTest but not in CMake
Description: 
When using CTest with launchers ("ctest -S script" with script setting
CTEST_USE_LAUNCHERS=ON), CTest expects xml files in Testing/*/Build/.
If it finds none, then no error/warning is reported.

Thus, if there is a misconfiguration where CMake is *not* configured with
launchers, then build errors are lost.

This happened to me because ctest_configure(OPTIONS
"-DCTEST_USE_LAUNCHERS=${CTEST_USE_LAUNCHERS}") is silently overwritten by
set(CTEST_CONFIGURE_COMMAND "...")


I report this issue first to have a public trace of this, to help others that
could run into this bug (it took me quite some time to understand the
misconfiguration...)

I don't necessarily expect a fix, because it's clearly a misconfiguration.

Maybe ctest_configure(OPTIONS) should not be silently ignored:
either append options to CTEST_CONFIGURE_COMMAND (but this could break
misconfigured ctest scripts that otherwise globally work); or log a warning
explaining that the OPTIONS is set but will be ignored (this is probably the
best solution).
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2015-05-06 12:57 trsystran      New Issue                                    
======================================================================



More information about the cmake-developers mailing list