[vtk-developers] vtkMath::Dot2D

[Bill Lorensen]

With a dashboard that is already colorful, you will have to look
through the results. This is one reason why it is crucial to keep the
dashboards green. Unfortunately, vtk is particularly colorful these
days.

If you check the Continuous during the day you can see if more or
fewer errors/warnings/test failures occur.

Also, you should sign up for e-mail notification. I assume someone
gave you directions on how to do this. If not, ask your vtk mentor.

Bill

On Thu, Dec 10, 2009 at 7:42 AM, David Doria <daviddoria+vtk at gmail.com> wrote:
> On Wed, Dec 9, 2009 at 8:52 PM, David Doria <daviddoria+vtk at gmail.com> wrote:
>> On Wed, Dec 9, 2009 at 8:40 PM, Bill Lorensen <bill.lorensen at gmail.com> wrote:
>>> Make sure all of vtk compiles after the change. If it requires changes
>>> to any vtk code you can be sure other people will have problems.
>>
>> Bill,
>>
>> The same 6 tests fail before and after the changes on my machine.
>>
>> The rule is don't commit anything between 4PM - ? AM EST, right? If
>> so, I'll commit in the morning and we'll see how the dashboard does.
>>
>> Thanks,
>>
>> David
>>
>
> Is there any way to tell if my change broke anything on the dashboard.
> In an ideal world, if the dashboard was completely green, I would just
> watch the continuous builds (which there seems to be only one of??)
> and see if they turn red. In the real world, if most of the builds
> have tests failing - how would I be alerted that my change caused more
> failures?
>
> Thanks,
>
> David
> _______________________________________________
> 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
>
>