[Paraview-developers] Dashboards

Utkarsh Ayachit utkarsh.ayachit at kitware.com
Mon Sep 26 10:57:59 EDT 2016


Yes. I believe Ken had even updated to push a new baseline. I wonder
if this changed further or somehow the baseline change didn't make it
through.

On Mon, Sep 26, 2016 at 10:53 AM, Cory Quammen <cory.quammen at kitware.com> wrote:
> Utkarsh,
>
> Do you suppose this
>
> https://open.cdash.org/testDetails.php?test=485843751&build=4565469
>
> was caused by Ken's recent rework of vtkCompositePolyDataMapper2?
>
>
> On Mon, Sep 26, 2016 at 10:08 AM, Utkarsh Ayachit
> <utkarsh.ayachit at kitware.com> wrote:
>>
>> Great! I know Ben is looking into the python27_d.lib issue on Miranda.
>>
>> I'll look at the "NumberOfComponentsDomain" test failure.
>>
>> Utkarsh
>>
>> On Mon, Sep 26, 2016 at 10:07 AM, Cory Quammen <cory.quammen at kitware.com>
>> wrote:
>> > I'll fix the ResetToVisible range errors. Looks like an alternate
>> > baseline
>> > for bigmac is needed.
>> >
>> > On Mon, Sep 26, 2016 at 9:38 AM, Andy Bauer <andy.bauer at kitware.com>
>> > wrote:
>> >>
>> >> I'll check out the FindDataDialog test failures.
>> >>
>> >> On Mon, Sep 26, 2016 at 9:11 AM, Utkarsh Ayachit
>> >> <utkarsh.ayachit at kitware.com> wrote:
>> >>>
>> >>> Folks,
>> >>>
>> >>> Dashboards are not in a good shape again. I know, given how slow
>> >>> dashboards can be in getting back on certain days, we sometimes take
>> >>> the leap of faith and merge things before all machines have responded
>> >>> (I am guilty of that too). But, we need to spot and address issues as
>> >>> soon as they are noticed. Next time, instead saying "failures are same
>> >>> as on master" in your merge request comments, try to fix the "master"
>> >>> failures. Ask the mailing list. Start working with someone to get it
>> >>> addressed! It's a collective responsibility to keep the dashboards
>> >>> green as it's helps all of us.
>> >>>
>> >>> On a related note, be kind to the dashboards. If your merge request is
>> >>> "WIP", try to hold off on testing requests until you're ready. Use
>> >>> `Do: test --oneshot` to avoid auto retesting when the MR is updated.
>> >>> Use `Do: test --stop` to stop further testing as soon as you spot an
>> >>> issue with your MR.
>> >>>
>> >>> Utkarsh
>> >>> _______________________________________________
>> >>> 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=Paraview-developers
>> >>>
>> >>> Follow this link to subscribe/unsubscribe:
>> >>> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> 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=Paraview-developers
>> >>
>> >> Follow this link to subscribe/unsubscribe:
>> >> http://public.kitware.com/mailman/listinfo/paraview-developers
>> >>
>> >
>> >
>> >
>> > --
>> > Cory Quammen
>> > Staff R&D Engineer
>> > Kitware, Inc.
>
>
>
>
> --
> Cory Quammen
> Staff R&D Engineer
> Kitware, Inc.


More information about the Paraview-developers mailing list