[vtk-developers] VTK Modular: Coverage and Valgrind process breakdown

[David Cole]

The AIX machine is not the coverage dashboard. It used to be
londinium. Unfortunately, there's a not-yet-fixed issue with gcov from
gcc 4.7 not working well with ctest. We have to get the fix into ctest
first to run it on a machine with gcc 4.7 -- if somebody else could
volunteer a machine using an earlier gcc to report VTK coverage, that
would be a good thing.

Here's a filtered view of coverage dashboards:

http://open.cdash.org/index.php?project=VTK&filtercount=2&showfilters=1&filtercombine=and&field1=hasdynamicanalysis/bool&compare1=1&value1=&field2=buildstarttime/date&compare2=84&value2=now

And of dynamic analysis dashboards:

http://open.cdash.org/index.php?project=VTK&filtercount=2&showfilters=1&filtercombine=and&field1=hasdynamicanalysis/bool&compare1=1&value1=&field2=buildstarttime/date&compare2=84&value2=now

You can scroll through those to see what changed from day to day,
going as far back as we have CDash data.


HTH,
David C.


On Tue, May 1, 2012 at 3:15 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> Folks,
>
> Now that VTK modular is settling in, two important software process
> components need attention.
>
> 1) Coverage:
> p90n03.pbm.ihost.com - AIX00F614-xlC is the machine that produces
> coverage. It has not been building for 22 days.
>
> 2) Valgrind has over 12000 defects. Prior to modularization it had 0 defects.
> http://open.cdash.org/viewDynamicAnalysis.php?buildid=2238424
> Seems that many of the defects are python related and need some
> valgrind suppressions. Once that is done, we can fix the real defects.
>
> I'm willing to help improve coverage and real valgrind defects, but
> dashboard maintainers need to address the compilation failures and
> valgrdin suppressions.
>
> Bill
> --
> Unpaid intern in BillsBasement at noware dot com
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>