[Paraview-developers] Paraview offscreen rendering and graphical unit tests
Maxim Torgonskiy
kriolog at gmail.com
Wed May 31 23:48:39 EDT 2017
Thanks Shawn,
I've launched 'ctest -R vtkRendering' in my docker image and it works
(99% tests passed, 1 tests failed out of 257). The only failed test is
' 789 - vtkRenderingCoreCxx-TestFollowerPicking (Failed)'.
If someone finds this helpful, I've build it in the docker
debian:stretch with the system llvm-dev, mesa 13.0.3 and paraview
5.3.0 (release from archive). The configuration arguments are the
following:
mesa (identical to wiki):
===================================
CXXFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \
CFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=31" \
--disable-xvmc \
--disable-glx \
--disable-dri \
--with-dri-drivers="" \
--with-gallium-drivers="swrast" \
--disable-shared-glapi \
--disable-egl \
--with-egl-platforms="" \
--enable-gallium-osmesa \
--enable-gallium-llvm=yes \
--enable-llvm-shared-libs \
--disable-gles1 \
--disable-gles2 \
--prefix=$installdir
===================================
paraview:
===================================
-DCMAKE_BUILD_TYPE:STRING=Release \
-DCMAKE_INSTALL_PREFIX:PATH=$installdir \
-DBUILD_SHARED_LIBS:BOOL=ON \
-DBUILD_TESTING:BOOL=ON \
\# -DPARAVIEW_ENABLE_PYTHON:BOOL=ON
\
-DPARAVIEW_ENABLE_PYTHON:BOOL=OFF \
-DPARAVIEW_ENABLE_WEB:BOOL=OFF \
-DPARAVIEW_BUILD_QT_GUI:BOOL=OFF \
-DPARAVIEW_BUILD_PLUGIN_GMVReader:BOOL=OFF \
-DVTK_USE_X:BOOL=OFF \
-DOPENGL_INCLUDE_DIR:PATH= \
-DOPENGL_gl_LIBRARY:FILEPATH= \
-DOPENGL_glu_LIBRARY:FILEPATH= \
-DVTK_OPENGL_HAS_OSMESA:BOOL=ON \
-DOSMESA_INCLUDE_DIR:PATH=$installdir_osmesa/include \
-DOSMESA_LIBRARY:FILEPATH=$installdir_osmesa/lib/libOSMesa.so
===================================
Thanks,
Maxim
2017-05-31 9:44 GMT-04:00 Shawn Waldon <shawn.waldon at kitware.com>:
> Hi Maxim,
>
> The dashboard machine amber8 isn't a docker container. It is Ubuntu machine
> with an OSMesa built according to the instructions on the wiki.
>
> It would help if you would share the errors you are getting from the tests
> so we have a better idea of what is going wrong. Without having any hint
> what is wrong it is hard to guess.
>
> A way to test if your OSMesa is working in Docker? Try running `ctest -R
> vtkRendering` and see if those tests pass. If they do, then OSMesa is
> working and something else is going wrong.
>
> HTH,
> Shawn
>
> On Tue, May 30, 2017 at 11:59 PM, Maxim Torgonskiy <kriolog at gmail.com>
> wrote:
>>
>> Hello,
>>
>> I need to launch paraview graphical tests in a docker image (debian
>> stretch). I'm trying to perform this with osmesa and I use its custom
>> version from the manual
>> (http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D) as well
>> as the libosmesa6-dev package. When I launch ctest with the default
>> paraview test directory, the 800 (rendering-related) tests from 2100
>> are failed. When I use cdash config from
>> https://open.cdash.org/buildSummary.php?buildid=4918000 the situation
>> is approximately the same.
>> If it's possible, could you please share me the missing part of the
>> puzzle (your current docker image, custom test direcrory
>> [/home/kitware/Dashboards/MyTests/ExternalData], etc) so that I can
>> repeat the result presented on the cdash board? And is there any
>> method to check that osmesa actually works in docker itself and with
>> paraview. A quick google search gives me nothing.
>>
>> Thanks,
>> Maxim
>> _______________________________________________
>> 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
>
>
More information about the Paraview-developers
mailing list