MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013143CMakeCTestpublic2012-04-18 06:512013-10-30 10:52
ReporterNils Gladitz 
Assigned ToNils Gladitz 
PrioritynormalSeverityminorReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOSOS Version
Product VersionCMake 2.8.7 
Target VersionFixed in VersionCMake 3.0 
Summary0013143: ctest_coverage runs gcov on gcda files outside the current build directory
DescriptionI've got a build client running CDash jobs for multiple projects all of which have distinct (parallel) source and build directories.

During a coverage run I saw gcov being called on gcda files of all projects rather than just the currently running project.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-04-18 06:51Nils GladitzNew Issue
2012-04-18 08:12Nils GladitzNote Added: 0029205
2012-08-11 21:35David ColeStatusnew => backlog
2012-08-11 21:35David ColeNote Added: 0030405
2013-10-30 10:51Nils GladitzNote Added: 0034295
2013-10-30 10:51Nils GladitzStatusbacklog => resolved
2013-10-30 10:51Nils GladitzFixed in Version => CMake 3.0
2013-10-30 10:51Nils GladitzResolutionopen => fixed
2013-10-30 10:51Nils GladitzAssigned To => Nils Gladitz
2013-10-30 10:52Nils GladitzStatusresolved => closed

Notes
(0029205)
Nils Gladitz   
2012-04-18 08:12   
I'm not too familiar with the code base but could it be because cmCTestCoverageHandler::Initialize() does not clear "TargetDirs"?

e.g. does it (and the handler?) get reused between possibly unrelated build jobs?
(0030405)
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.
(0034295)
Nils Gladitz   
2013-10-30 10:51   
Fixed by http://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=f2572b04c5c77c79f07cc7fb094fbd97770e18e0;hp=601d40358e8183519a5fcc018cfc174cc283d346 [^]