[vtk-developers] Experimental buildbot builds are distracting

[Cory Quammen]

Thanks, Shawn.

What does the new "new" designation mean? Can we ignore those builds?

Thanks,
Cory

On Mon, Oct 26, 2015 at 10:04 AM, Shawn Waldon <shawn.waldon at kitware.com>
wrote:

> Cory,
>
> As of last Tuesday, the experimental builds no longer show up in the
> messages at all.  We still have to wait for them to complete (buildbot
> doesn't have a hook for 'when a subset of builds finishes'), but the
> messages pushed to gitlab should only contain results from expected builds.
>
> Shawn
>
> On Mon, Oct 26, 2015 at 9:30 AM, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
>> I would be great if the experimental builds in the gitlab messages be
>> listed at the bottom so that they can more easily be ignored.
>>
>> Cory
>>
>> On Tue, Oct 20, 2015 at 11:50 AM, Ben Boeckel <ben.boeckel at kitware.com>
>> wrote:
>>
>>> On Tue, Oct 20, 2015 at 08:00:55 -0400, Ken Martin wrote:
>>> > I can see the experimental buildbot group being useful for staging new
>>> > builbots to see if they would be green, or moving master buildbots
>>> down if
>>> > an OS upgrade breaks something and it has not been fixed yet (Trey
>>> would
>>> > have been a candidate for this)
>>>
>>> The problem with downgrading is that we generally have minimal cover
>>> over the feature sets we're testing. For example, trey is the only
>>> osx+python3 tester and the only osx+qt+opengl2 (kamino is just osx+qt)
>>> tester. And since the experimentals are generally ignored…
>>>
>>> > But having long running persistent experimental failing buildbots
>>> > seems of questionable value.  I do not consider experimental buildbots
>>> > in evaluating the quality of a topic.
>>>
>>> Agreed. For VTK, agora should be fixed and made expected as it's the
>>> only machine testing the Intel compiler and PGI. Kargad is flaky and
>>> probably worth deciding whether to boot off or not. Amber10 has this
>>> error:
>>>
>>> ..\..\..\..\source\ThirdParty\netcdf\vtknetcdf\libsrc4\nc4hdf.c(3666):
>>> error C2177: constant too big
>>> ..\..\..\..\source\ThirdParty\netcdf\vtknetcdf\libsrc4\nc4hdf.c(3666):
>>> error C2177: constant too big
>>>
>>> which is weird since every other Win64 builder doesn't care. Is it
>>> VS2010-specific? Unlikely since ParaView has 2010 builders which don't
>>> have this error. And it looks like I need to get a Qt4 build on nemesis
>>> which has QtWebKit enabled (or disable the webkit-using modules).
>>>
>>> --Ben
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Search the list archives at:
>>> http://markmail.org/search/?q=vtk-developers
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/vtk-developers
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at: http://markmail.org/search/?q=vtk-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/vtk-developers
>>
>>
>>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20151026/9ca7ed8e/attachment.html>