[vtk-developers] Valgrind defects are zero!

[David Cole]

The 21 minutes is just for the ctest_test call. The time for the
ctest_memcheck call is not shown on the dashboard. They are both run
on this particular dashboard.

See my other email re: log files...



On Thu, Dec 8, 2011 at 3:39 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
> amber2.kitware Debian4-x64-gcc-Valgrind is the valgrind machine. It
> takes 21 minutes to run the tests.
>
> tha's the good news. The bad news is that python and tcl wrapping are
> turned off. That means about 800 tests are not being run through
> valgrind.
>
> Sean, if you have a machine that could turn on tcl wrapping, it would
> be great. It will take a few nights to get all of the tcl suppression
> working.
>
> On Thu, Dec 8, 2011 at 3:22 PM, Sean McBride <sean at rogue-research.com> wrote:
>> On Thu, 8 Dec 2011 15:12:22 -0500, David Cole said:
>>
>>>All fine suggestions in theory, but running a valgrind dashboard on
>>>every single gerrit topic will be quite time consuming.
>>
>> Indeed.  And AFAICT, there is only *1* build machine running valgrind.  Would be nice to have some redundancy there.  We have a mostly-idle machine that could (maybe) do this nightly.
>>
>> cdash's 'Dynamic Analysis' section doesn't seem to discuss runtime.... about how long does it take to run all VTK tests in valgrind?  (our machine in question is an i7.)
>>
>> Cheers,
>>
>> --
>> ____________________________________________________________
>> Sean McBride, B. Eng                 sean at rogue-research.com
>> Rogue Research                        www.rogue-research.com
>> Mac Software Developer              Montréal, Québec, Canada
>>
>>
>> _______________________________________________
>> 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
>>
>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com