[vtk-developers] Valgrind defects are zero!
david.partyka at kitware.com
Thu Dec 8 15:42:24 EST 2011
Geeze 10 hours? That machine is also a P4 pos from 2006.
On Thu, Dec 8, 2011 at 3:38 PM, David Cole <david.cole at kitware.com> wrote:
> We can do way better than guess, since we have access to the machine.
> Analyze the log file time stamps left in Testing/Temporary:
> kitware at amber2:~/Dashboards/MyTests/VTK-valgrind/Testing/Temporary$
> ls -lart *.log
> -rw-r--r-- 1 kitware kitware 0 2011-12-07 23:12 LastStart.log
> -rw-r--r-- 1 kitware kitware 1499 2011-12-07 23:12
> -rw-r--r-- 1 kitware kitware 28792 2011-12-07 23:13
> -rw-r--r-- 1 kitware kitware 846656 2011-12-07 23:49
> -rw-r--r-- 1 kitware kitware 4475923 2011-12-08 00:11
> -rw-r--r-- 1 kitware kitware 85 2011-12-08 10:49
> -rw-r--r-- 1 kitware kitware 4627135 2011-12-08 10:49
> -rw-r--r-- 1 kitware kitware 284 2011-12-08 10:49
> LastTest_20111208-0100.log was last modified at 11 minutes after
> midnight (00:11)
> LastDynamicAnalysis_20111208-0100.log was last modified at 10:49 this
> Unless my math is wrong, or somebody re-ran just the valgrind portion
> by hand this morning, the dynamic analysis run on this machine took 10
> hours and 38 minutes today.
> Dave C.
> On Thu, Dec 8, 2011 at 3:26 PM, David Partyka <david.partyka at kitware.com>
> > I would guesstimate an hour or two to run all ~1000ish tests on modern
> > hardware. It takes a while to get the supression file straightened out,
> > will take several submission iterations just so you know what you're
> > yourself into.
> > There aren't that many valgrind submissions because we don't have many
> > machines with GPUs. We do have two new machines that I would like to
> > valgrind dashboards on but it hasn't trickeld up in priority for me yet
> > 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
> >> 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
> >> 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtk-developers