[vtk-developers] Failing test rendering problem

David Thompson david.thompson at kitware.com
Thu Jul 2 09:37:25 EDT 2015


Hi Mathieu,

Thanks for looking into this. I've been noticing failures like that in VTK and in some projects that use it. However, given the number of image tests that VTK runs, adding 2s of delay to each one would slow the dashboards down too much to be usable. However, it is a great start on figuring out how to fix the issue. I don't see anywhere that vtkRenderWindow::WaitForCompletion() (which calls glFinish) gets called when grabbing the framebuffer. Perhaps adding this would be faster than a timer. Can you verify that it works? If so, maybe we can figure out where to add it to avoid slowing production code down for testing.

	Thanks,
	David

> I have some problem with tests wich render and compare to an image.
> 
> Lots of test do the rendering which can be seen on screen, but the generated image is completelly black ( or white ) and the test fail.
> 
> Most of these failing tests are python test but not only.
> The list of failing tests is attached.
> 
> I've tried to understood what was going on, so i've tried to fix 
> sync3dAll.py
> 
> Adding :      
>         import time
>         time.sleep(1)
>         renWin.Render()
>         time.sleep(1)
> 
> after the first render() did the trick. It look like the renderring is not done fast enough ans the produced image is empty as it has not yet been rendered.
> 
> Any help appreciated.
> 
> Mathieu Westphal
> <tests>_______________________________________________
> 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
> 



More information about the vtk-developers mailing list