[vtk-developers] Uploading full test images to CDash

Moreland, Kenneth kmorel at sandia.gov
Tue May 19 19:08:33 EDT 2009


Although I try to avoid it, occasionally I create or modify a test that requires multiple baseline images because different GPUs will generate images with enough differences.  Doing this is easy enough (just check in the extra baseline images), but I don't have access to most of the VTK and ParaView dashboards.  In order to get the image, I have to track down someone with access to the machine and ask them to check in the image for me.

In my mind it is backwards to have the dashboard maintainer making the decision on whether a test legitimately failed or has innocuous image differences.  Rather, the person creating the test should make the determination.  Thus, it makes sense for the image to be uploaded to the dashboard where everyone, most importantly the test coder, has access, can download a copy, and check in a new baseline.

I recently met some of the CMake/CDash developers and asked them for this feature.  They told me the functionality is already in CDash; I only need to instruct CTest to upload the files I want to show up.  As it turns out, with only a couple of small changes I can implement this in VTK (and by proxy in ParaView).  The attached VTK patch implements the full image upload.  Are there any objections to checking this in?

-Ken

   ****      Kenneth Moreland
    ***      Sandia National Laboratories
***********
*** *** ***  email: kmorel at sandia.gov
**  ***  **  phone: (505) 844-8919
    ***      web:   http://www.cs.unm.edu/~kmorel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20090519/72773255/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: CDashFullTestImages.patch
Type: application/octet-stream
Size: 3736 bytes
Desc: CDashFullTestImages.patch
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20090519/72773255/attachment-0001.obj>


More information about the vtk-developers mailing list