[vtk-developers] The dashboard: tarvalon gerrit builds
robert.maynard at kitware.com
Fri Apr 5 10:55:36 EDT 2013
I haven't been able to track down why Tarvalon has regressed on the shader
tests, so I will be suppressing those tests on Tarvalon until we can
determine the root cause.
On Thu, Apr 4, 2013 at 10:16 AM, Berk Geveci <berk.geveci at kitware.com>wrote:
> Hi David,
> Your tone was just fine. I didn't sense any negativity. At least, not more
> than I have been feeling with my Gerrit reviews coming unclean for a few
> days :-)
> I encourage everyone involved in VTK development to keep an eye on
> dashboards and specially the Gerrit ones. If there is something suspicious,
> please make noise here so that we can address them. I have been trying to
> keep an eye on the dashboard but I miss things - such as issues with Gerrit
> builds when I am not pushing to Gerrit.
> On Thu, Apr 4, 2013 at 10:06 AM, David Cole <dlrdave at aol.com> wrote:
>> Thanks for the info, Berk. And for the effort, Rob!
>> I was merely trying to start a discussion with some facts and some
>> questions. I didn’t see anything already on the mailing list about any
>> pending work, just that the machine had come back up after our previous
>> inquiry about “where did it go?”
>> Sorry if my tone had any negativity to it this morning... I was
>> frustrated by a lack of Windows-confirmation for this pending topic:
>> *From:* Berk Geveci
>> *Sent:* Thursday, April 4, 2013 8:37 AM
>> *To:* David Cole; Robert Maynard
>> *Cc:* VTK Developers
>> Hi David,
>> These errors are machine-caused not VTK-caused. I asked Rob M. to
>> investigate. It may be due to updated ATI drivers. Once he figures out what
>> is causing them, he will clean it up. This should happen very soon.
>> On Thu, Apr 4, 2013 at 6:22 AM, David Cole <dlrdave at aol.com> wrote:
>>> Gerrit builds with 0 build errors from tarvalon since Feb 20th:
>>> Sort the above results by build time, to look at things in date order.
>>> - Recurring persistent test failures were eliminated and reduced to 0 at
>>> the VTK dash-a-thon on Feb. 27th (yay!)
>>> - From Feb. 27th to Mar. 7th, there were predominantly 0 test failures
>>> on these builds. When it was non-0, it typically indicated a real problem
>>> with the topic being tested. Or with a VTKData change. Quite helpful.
>>> - From Mar. 8th to Mar. 21st, there were no submissions from this
>>> machine. It was apparently down for that long.
>>> - Beginning Mar. 22nd and continuing to the most recent submission,
>>> there are 10 recurring test failures again.
>>> - sometime between Mar. 8th and 22nd, changes were merged that caused
>>> these test failures (or perhaps something changed on the machine while it
>>> was on vacation?)
>>> - tarvalon is now only good as a gerrit submitter for detecting newly
>>> introduced Windows compile/link errors or warnings, which is still somewhat
>>> useful. But... since tests persistently and recurringly fail, it's *not*
>>> very useful at detecting runtime behavior changes introduced by gerrit
>>> - Can we, the VTK developer community, fix it again and keep it fixed?
>>> Or do we need a dash-a-thon every month? ;-)
>>> - Can anybody else volunteer an additional Windows gerrit build?
>>> I, for one, would appreciate a clean gerrit Windows build. I *did*
>>> appreciate it for the 9 brief days that we had it...
>>> Thanks for considering,
>>> David C.
>>> Powered by www.kitware.com
>>> Visit other Kitware open-source projects at http://www.kitware.com/**
>>> Follow this link to subscribe/unsubscribe:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vtk-developers