I've verified that the gdca files are there. And it displays coverage
on CDash -- indicating coverage reports are being pushed to the CDash
server -- but reports zero coverage.
I am using a SuperBuild/ExternalProject build system but for the
purposes of dashboards, I do the top level build, then g
Great!
These look like the important lines to fix my coverage issue with Superbuilds:
# HACK Unfortunately ctest_coverage ignores the BUILD argument, try to
force it...
file(READ ${slicer_build_dir}/CMakeFiles/TargetDirectories.txt
slicer_build_coverage_dirs)
file(APPEND "${CT
Hi Brad,
Consider looking at
https://github.com/Slicer/Slicer/blob/master/CMake/SlicerDashboardDriverScript.cmake#L246
Hth
Jc
On Tue, Apr 24, 2012 at 9:13 AM, Bradley Lowekamp wrote:
> Hello,
>
> Are both of these project using SuperBuilds?
>
> I know with SimpleITK I was unable to get coverage
Hello,
Are both of these project using SuperBuilds?
I know with SimpleITK I was unable to get coverage to work in the SuperBuild
structure. To get coverage we are doing the project, with its self not being an
ExternalProject. However, valgrind works just fine in the Superbuild structure.
I did
Ugh. You're probably doing everything right, and there's just a bug of some
sort. Unfortunately, debugging these things is neither easy nor fun.
First, look for Coverage*.log files in the Testing/ subdirectories of your
build tree. Are there any errors mentioned in there?
Next, verify that there
cmake: 2.8.6
gcc/g++: 4.4.6-3
Red Hate Enterprise Linux 6.2
I follow the instructions here: http://www.cmake.org/Wiki/CTest/Coverage
And I have 2 different dashboards that report zero coverage:
http://testing.psychiatry.uiowa.edu/CDash/index.php?project=BRAINSStandalone
http://testing.psychiatry
