MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012947CMake(No Category)public2012-02-08 19:272016-06-10 14:31
ReporterMatthew McCormick 
Assigned ToKitware Robot 
PrioritynormalSeveritymajorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0012947: ctest_coverage not submitting coverage with superbuild setups.
DescriptionSee

  http://www.cdash.org/CDash/viewNotes.php?buildid=1989226 [^]

The "file( APPEND ${CTEST_BINARY_DIRECTORY}/CMakeFiles/TargetDirectories.txt" ... is required to get processing of the coverage for this superbuild project. Otherwise, the ctest_coverage command results in a message that Coverage.xml is not found, and the coverage submission does not occur.

Also, it is not intuitive that the path sent to "ctest_coverage( BUILD" is ${CTEST_BINARY_DIRECTORY} instead of ${CTEST_BINARY_DIRECTORY}/Farsight in this case. That is, I would expect that the build directory for the project instead of the build directory for the superbuild should be passed to "ctest_coverage( BUILD" as is done with "ctest_build( BUILD". However, ${CTEST_BINARY_DIRECTORY}/Farsight is passed, it does not submit the correct coverage results.
Steps To ReproduceTested that the bug is present with CMake master per 2012-02-08.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-02-08 19:27Matthew McCormickNew Issue
2012-08-11 21:09David ColeStatusnew => backlog
2012-08-11 21:09David ColeNote Added: 0030363
2016-06-10 14:28Kitware RobotNote Added: 0041982
2016-06-10 14:28Kitware RobotStatusbacklog => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0030363)
David Cole   
2012-08-11 21:09   
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.
(0041982)
Kitware Robot   
2016-06-10 14:28   
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.