Geeze 10 hours? That machine is also a P4 pos from 2006.<br><br><div class="gmail_quote">On Thu, Dec 8, 2011 at 3:38 PM, David Cole <span dir="ltr"><<a href="mailto:david.cole@kitware.com">david.cole@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">We can do way better than guess, since we have access to the machine.<br>
Analyze the log file time stamps left in Testing/Temporary:<br>
<br>
kitware@amber2:~/Dashboards/MyTests/VTK-valgrind/Testing/Temporary$<br>
ls -lart *.log<br>
-rw-r--r-- 1 kitware kitware 0 2011-12-07 23:12 LastStart.log<br>
-rw-r--r-- 1 kitware kitware 1499 2011-12-07 23:12<br>
LastUpdate_20111208-0100.log<br>
-rw-r--r-- 1 kitware kitware 28792 2011-12-07 23:13<br>
LastConfigure_20111208-0100.log<br>
-rw-r--r-- 1 kitware kitware 846656 2011-12-07 23:49<br>
LastBuild_20111208-0100.log<br>
-rw-r--r-- 1 kitware kitware 4475923 2011-12-08 00:11<br>
LastTest_20111208-0100.log<br>
-rw-r--r-- 1 kitware kitware 85 2011-12-08 10:49<br>
LastTestsFailed_20111208-0100.log<br>
-rw-r--r-- 1 kitware kitware 4627135 2011-12-08 10:49<br>
LastDynamicAnalysis_20111208-0100.log<br>
-rw-r--r-- 1 kitware kitware 284 2011-12-08 10:49<br>
LastSubmit_20111208-0100.log<br>
<br>
LastTest_20111208-0100.log was last modified at 11 minutes after<br>
midnight (00:11)<br>
LastDynamicAnalysis_20111208-0100.log was last modified at 10:49 this morning.<br>
<br>
Unless my math is wrong, or somebody re-ran just the valgrind portion<br>
by hand this morning, the dynamic analysis run on this machine took 10<br>
hours and 38 minutes today.<br>
<br>
<br>
Cheers,<br>
Dave C.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On Thu, Dec 8, 2011 at 3:26 PM, David Partyka <<a href="mailto:david.partyka@kitware.com">david.partyka@kitware.com</a>> wrote:<br>
> I would guesstimate an hour or two to run all ~1000ish tests on modern<br>
> hardware. It takes a while to get the supression file straightened out, it<br>
> will take several submission iterations just so you know what you're getting<br>
> yourself into.<br>
><br>
> There aren't that many valgrind submissions because we don't have many linux<br>
> machines with GPUs. We do have two new machines that I would like to create<br>
> valgrind dashboards on but it hasn't trickeld up in priority for me yet :-/<br>
><br>
> On Thu, Dec 8, 2011 at 3:22 PM, Sean McBride <<a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a>><br>
> wrote:<br>
>><br>
>> On Thu, 8 Dec 2011 15:12:22 -0500, David Cole said:<br>
>><br>
>> >All fine suggestions in theory, but running a valgrind dashboard on<br>
>> >every single gerrit topic will be quite time consuming.<br>
>><br>
>> Indeed. And AFAICT, there is only *1* build machine running valgrind.<br>
>> Would be nice to have some redundancy there. We have a mostly-idle machine<br>
>> that could (maybe) do this nightly.<br>
>><br>
>> cdash's 'Dynamic Analysis' section doesn't seem to discuss runtime....<br>
>> about how long does it take to run all VTK tests in valgrind? (our machine<br>
>> in question is an i7.)<br>
>><br>
>> Cheers,<br>
>><br>
>> --<br>
>> ____________________________________________________________<br>
>> Sean McBride, B. Eng <a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a><br>
>> Rogue Research <a href="http://www.rogue-research.com" target="_blank">www.rogue-research.com</a><br>
>> Mac Software Developer Montréal, Québec, Canada<br>
>><br>
>><br>
>> _______________________________________________<br>
>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>><br>
>> Visit other Kitware open-source projects at<br>
>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>><br>
>> Follow this link to subscribe/unsubscribe:<br>
>> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>><br>
><br>
</div></div></blockquote></div><br>