[vtk-developers] cdash - updates

[David Cole]

No problem. The lesson (maybe?) here is to commit new/updated data first....
A new data file will not trigger a continuous rebuild. But a commit into VTK
will. If the data is not there when the continuous begins, then the test
will fail until the next time.

And thanks for verifying it was a false alarm.



On Mon, Jul 7, 2008 at 5:34 PM, Dean Inglis <dean.inglis at camris.ca> wrote:

>  dashmacmini1.kitware
>
> DASH3.kitware
>
>
>
> Both have corrected themselves.  I committed the
>
> test image after the code changes, so I guess the
>
> next update and continuous build caught it.  Sorry,
>
> false alarm….
>
>
>
> Dean
>
>
>
>
>
> I thought all of them already were. Which one did not update VTKData
> properly?
>
>  2008/7/7 Dean Inglis <dean.inglis at sympatico.ca>:
>
> I committed changes to vtkOrientationMarkerWidget
>
> and committed a new Baseline image to VTKData for
>
> its test.  Can the continuous build cmake scripts be
>
> modified so that VTKData is cvs updated prior to
>
> running tests?
>
>
>
> Dean
>
>
>
>
> _______________________________________________
> vtk-developers mailing list
> vtk-developers at vtk.org
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20080707/0b31848c/attachment.html>