MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015557CMakeCTestpublic2015-05-06 12:572016-06-10 14:31
Reportertrsystran 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 3.2.1 
Target VersionFixed in Version 
Summary0015557: CTest misses build errors if launchers enabled in CTest but not in CMake
DescriptionWhen 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).
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-05-06 12:57trsystranNew Issue
2016-06-10 14:29Kitware RobotNote Added: 0042773
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0042773)
Kitware Robot   
2016-06-10 14:29   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.