[vtk-developers] Addition flag for valgrind

[David E DeMarle]

I ended up with 1.5. The timeout is doubled to 1000s now, and the tests
that still timed out have been disabled.

David E DeMarle
Kitware, Inc.
R&D Engineer
21 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-881-4909


On Wed, Mar 6, 2013 at 9:50 AM, Bill Lorensen <bill.lorensen at gmail.com>wrote:

> +1 for #1
>
>
> On Wednesday, March 6, 2013, Kyle Lutz wrote:
>
>> On Wed, Mar 6, 2013 at 9:35 AM, David E DeMarle
>> <dave.demarle at kitware.com> wrote:
>> > But valgrind is getting slow. I may have to remove that flag from
>> karego-at
>> > valgrind.
>> >
>> > --track-origins slows the tests down significantly - as evidenced by
>> the new
>> >>500s timeout test failures on the valgrind results
>> > (http://open.cdash.org/viewDynamicAnalysis.php?buildid=2836814). There
>> is
>> > some free time available overnight on that machine, so I'm checking how
>> much
>> > extra time the failing tests require. I had kind of wanted that time
>> though
>> > to turn on more tests...
>> >
>> > What is our preference:
>> > 1) keep the flag, increase the timeout, and continue to test what we do
>> > 2) disable just these slow tests on that machine and possibly turn on
>> other
>> > tests (MPI, Qt, Tcl, Python)
>> > 3) remove the flag and turn on more tests
>> >
>> > I'm leaning toward 1. When we get and setup a newer test machine it
>> should
>> > be less of an issue and we can have out cake and eat it too.
>>
>> +1 for #1.
>>
>
>
> --
> Unpaid intern in BillsBasement at noware dot com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20130307/7874c5f7/attachment.html>