View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0012947 | CMake | (No Category) | public | 2012-02-08 19:27 | 2016-06-10 14:31 | ||||
Reporter | Matthew McCormick | ||||||||
Assigned To | Kitware Robot | ||||||||
Priority | normal | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | moved | ||||||
Platform | OS | OS Version | |||||||
Product Version | |||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0012947: ctest_coverage not submitting coverage with superbuild setups. | ||||||||
Description | See 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 Reproduce | Tested that the bug is present with CMake master per 2012-02-08. | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0030363) David Cole (manager) 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 (administrator) 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. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2012-02-08 19:27 | Matthew McCormick | New Issue | |
2012-08-11 21:09 | David Cole | Status | new => backlog |
2012-08-11 21:09 | David Cole | Note Added: 0030363 | |
2016-06-10 14:28 | Kitware Robot | Note Added: 0041982 | |
2016-06-10 14:28 | Kitware Robot | Status | backlog => resolved |
2016-06-10 14:28 | Kitware Robot | Resolution | open => moved |
2016-06-10 14:28 | Kitware Robot | Assigned To | => Kitware Robot |
2016-06-10 14:31 | Kitware Robot | Status | resolved => closed |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |