MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0012609CMakeCTestpublic2011-12-06 08:112016-06-10 14:31
ReporterMathieu Malaterre 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionCMake 2.8.5 
Target VersionFixed in Version 
Summary0012609: Report when CTEST_COVERAGE_COMMAND is not set
DescriptionWhen CTEST_COVERAGE_COMMAND is not set, ctest reports:


Problem running coverage on file: /home/ctest/Dashboards/My Tests/openjpeg-b15-linux_gcc44_gcov-v1.5-debug/tests/CMakeFiles/comparePGXimages.dir/__/applications/common/opj_getopt.c.gcda
Command produced error: No such file or directory
.No such file or directory


The output is confusing, it would be nice if cmCTestCoverageHandler::HandleGCovCoverage would test if

  std::string gcovCommand
    = this->CTest->GetCTestConfiguration("CoverageCommand");

is empty or not.
Steps To Reproduce
Additional InformationWhen looking at the debug log, it is clear that gcov is missing:


Performing coverage: 1.32317e+09
* Run coverage for: /home/ctest/Dashboards/My Tests/openjpeg-b15-linux_gcc44_gcov-v1.5-debug/applications/codec/CMakeFiles/image_to_j2k.dir
  Command: "" -l -p -o "/home/ctest/Dashboards/My Tests/openjpeg-b15-linux_gcc44_gcov-v1.5-debug/applications/codec/CMakeFiles/image_to_j2k.dir" "/home/ctest/Dashboards/My Tests/openjpeg-b15-linux_gcc44_gcov-v1.5-debug/applications/codec/CMakeFiles/image_to_j2k.dir/image_to_j2k.c.gcda"
  Output:
  Errors: No such file or directory
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-12-06 08:11Mathieu MalaterreNew Issue
2012-08-11 21:09David ColeStatusnew => backlog
2012-08-11 21:09David ColeNote Added: 0030338
2016-06-10 14:28Kitware RobotNote Added: 0041940
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
(0030338)
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.
(0041940)
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.