<div dir="ltr"><div><div><div>Hi Maxim,<br> Try running the following script with pvpython and see what your results are:<br><div style="margin-left:40px"><span style="font-family:monospace,monospace"></span><span style="font-family:monospace,monospace"># CheckOpenGLInfo.py</span><br><span style="font-family:monospace,monospace">from vtk.<wbr>vtkPVClientServerCoreRendering import vtkPVOpenGLInformation</span><br><span style="font-family:monospace,monospace">info = vtkPVOpenGLInformation()</span><br><span style="font-family:monospace,monospace">info.CopyFromObject(None)</span><br><span style="font-family:monospace,monospace">print("Vendor:   %s" % info.GetVendor())</span><br><span style="font-family:monospace,monospace">print("Version:  %s" % info.GetVersion())</span><br><span style="font-family:monospace,monospace">print("Renderer: %s" % info.GetRenderer())</span><br></div></div><br></div>With Mesa-13.0.3, using the build instructions from <a href="http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D" target="_blank">http://www.paraview.org/Wiki/<wbr>ParaView/ParaView_And_Mesa_3D</a>, I get:<br><span style="font-family:monospace,monospace">Vendor:   VMware, Inc.<br>Version:  3.3 (Core Profile) Mesa 13.0.3 (git-bec0411)<br>Renderer: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits)</span><br><br></div>Or, if I explicitly set GALLIUM_DRIVER=swr:<br><span style="font-family:monospace,monospace">SWR detected AVX2<br>Vendor:   Intel Corporation<br>Version:  3.3 (Core Profile) Mesa 13.0.3 (git-bec0411)<br>Renderer: Gallium 0.4 on SWR</span><br><br><div class="gmail_extra"><div><div class="m_-2875950348648499645gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">----------<br>Chuck Atkins<br>Staff R&D Engineer, Scientific Computing<br>Kitware, Inc.<br></div></div></div></div></div></div></div><br><div class="gmail_quote">On Thu, Jun 1, 2017 at 12:03 AM, Maxim Torgonskiy <span dir="ltr"><<a href="mailto:kriolog@gmail.com" target="_blank">kriolog@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">And I've just verified, it doesn't work (18% tests passed, 210 tests<br>
failed out of 257) with the system libosmesa6-dev (13.0.6-1+b2). The<br>
output could be found here:<br>
<a href="https://gist.github.com/kriolog/10af62df8645bc61e30535023d2fb824" rel="noreferrer" target="_blank">https://gist.github.com/kriolo<wbr>g/10af62df8645bc61e30535023d2f<wbr>b824</a><br>
<div class="m_-2875950348648499645HOEnZb"><div class="m_-2875950348648499645h5"><br>
2017-05-31 23:48 GMT-04:00 Maxim Torgonskiy <<a href="mailto:kriolog@gmail.com" target="_blank">kriolog@gmail.com</a>>:<br>
> Thanks Shawn,<br>
><br>
> I've launched 'ctest -R vtkRendering' in my docker image and it works<br>
> (99% tests passed, 1 tests failed out of 257). The only failed test is<br>
> ' 789 - vtkRenderingCoreCxx-TestFollow<wbr>erPicking (Failed)'.<br>
><br>
> If someone finds this helpful, I've build it in the docker<br>
> debian:stretch with the system llvm-dev, mesa 13.0.3 and paraview<br>
> 5.3.0 (release from archive). The configuration arguments are the<br>
> following:<br>
><br>
> mesa (identical to wiki):<br>
> ==============================<wbr>=====<br>
>   CXXFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=<wbr>31" \<br>
>   CFLAGS="-O2 -g -DDEFAULT_SOFTWARE_DEPTH_BITS=<wbr>31" \<br>
>   --disable-xvmc \<br>
>   --disable-glx \<br>
>   --disable-dri \<br>
>   --with-dri-drivers="" \<br>
>   --with-gallium-drivers="swras<wbr>t" \<br>
>   --disable-shared-glapi \<br>
>   --disable-egl \<br>
>   --with-egl-platforms="" \<br>
>   --enable-gallium-osmesa \<br>
>   --enable-gallium-llvm=yes \<br>
>   --enable-llvm-shared-libs \<br>
>   --disable-gles1 \<br>
>   --disable-gles2 \<br>
>   --prefix=$installdir<br>
> ==============================<wbr>=====<br>
><br>
> paraview:<br>
> ==============================<wbr>=====<br>
>   -DCMAKE_BUILD_TYPE:STRING=Rel<wbr>ease                                            \<br>
>   -DCMAKE_INSTALL_PREFIX:PATH=$<wbr>installdir                                      \<br>
>   -DBUILD_SHARED_LIBS:BOOL=ON                                                  \<br>
>   -DBUILD_TESTING:BOOL=ON                                                      \<br>
> \#   -DPARAVIEW_ENABLE_PYTHON:<wbr>BOOL=ON<br>
>            \<br>
>   -DPARAVIEW_ENABLE_PYTHON:<wbr>BOOL=OFF                                            \<br>
>   -DPARAVIEW_ENABLE_WEB:BOOL=<wbr>OFF                                               \<br>
>   -DPARAVIEW_BUILD_QT_GUI:BOOL=<wbr>OFF                                             \<br>
>   -DPARAVIEW_BUILD_PLUGIN_GMVRe<wbr>ader:BOOL=OFF                                   \<br>
>   -DVTK_USE_X:BOOL=OFF                                                         \<br>
>   -DOPENGL_INCLUDE_DIR:PATH=                                                   \<br>
>   -DOPENGL_gl_LIBRARY:FILEPATH=<wbr>                                                \<br>
>   -DOPENGL_glu_LIBRARY:<wbr>FILEPATH=                                               \<br>
>   -DVTK_OPENGL_HAS_OSMESA:BOOL=<wbr>ON                                              \<br>
>   -DOSMESA_INCLUDE_DIR:PATH=$in<wbr>stalldir_osmesa/include                         \<br>
>   -DOSMESA_LIBRARY:FILEPATH=$in<wbr>stalldir_osmesa/lib/libOSMesa.<wbr>so<br>
> ==============================<wbr>=====<br>
><br>
> Thanks,<br>
> Maxim<br>
><br>
> 2017-05-31 9:44 GMT-04:00 Shawn Waldon <<a href="mailto:shawn.waldon@kitware.com" target="_blank">shawn.waldon@kitware.com</a>>:<br>
>> Hi Maxim,<br>
>><br>
>> The dashboard machine amber8 isn't a docker container.  It is Ubuntu machine<br>
>> with an OSMesa built according to the instructions on the wiki.<br>
>><br>
>> It would help if you would share the errors you are getting from the tests<br>
>> so we have a better idea of what is going wrong.  Without having any hint<br>
>> what is wrong it is hard to guess.<br>
>><br>
>> A way to test if your OSMesa is working in Docker?  Try running `ctest -R<br>
>> vtkRendering` and see if those tests pass.  If they do, then OSMesa is<br>
>> working and something else is going wrong.<br>
>><br>
>> HTH,<br>
>> Shawn<br>
>><br>
>> On Tue, May 30, 2017 at 11:59 PM, Maxim Torgonskiy <<a href="mailto:kriolog@gmail.com" target="_blank">kriolog@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Hello,<br>
>>><br>
>>> I need to launch paraview graphical tests in a docker image (debian<br>
>>> stretch). I'm trying to perform this with osmesa and I use its custom<br>
>>> version from the manual<br>
>>> (<a href="http://www.paraview.org/Wiki/ParaView/ParaView_And_Mesa_3D" rel="noreferrer" target="_blank">http://www.paraview.org/Wiki/<wbr>ParaView/ParaView_And_Mesa_3D</a>) as well<br>
>>> as the libosmesa6-dev package. When I launch ctest with the default<br>
>>> paraview test directory, the 800 (rendering-related) tests from 2100<br>
>>> are failed. When I use cdash config from<br>
>>> <a href="https://open.cdash.org/buildSummary.php?buildid=4918000" rel="noreferrer" target="_blank">https://open.cdash.org/buildSu<wbr>mmary.php?buildid=4918000</a> the situation<br>
>>> is approximately the same.<br>
>>> If it's possible, could you please share me the missing part of the<br>
>>> puzzle (your current docker image, custom test direcrory<br>
>>> [/home/kitware/Dashboards/MyTe<wbr>sts/ExternalData], etc) so that I can<br>
>>> repeat the result presented on the cdash board? And is there any<br>
>>> method to check that osmesa actually works in docker itself and with<br>
>>> paraview. A quick google search gives me nothing.<br>
>>><br>
>>> Thanks,<br>
>>> Maxim<br>
>>> ______________________________<wbr>_________________<br>
>>> Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
>>><br>
>>> Visit other Kitware open-source projects at<br>
>>> <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensou<wbr>rce/opensource.html</a><br>
>>><br>
>>> Search the list archives at:<br>
>>> <a href="http://markmail.org/search/?q=Paraview-developers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>Paraview-developers</a><br>
>>><br>
>>> Follow this link to subscribe/unsubscribe:<br>
>>> <a href="http://public.kitware.com/mailman/listinfo/paraview-developers" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/paraview-develope<wbr>rs</a><br>
>><br>
>><br>
______________________________<wbr>_________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/opensou<wbr>rce/opensource.html</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=Paraview-developers" rel="noreferrer" target="_blank">http://markmail.org/search/?q=<wbr>Paraview-developers</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview-developers" rel="noreferrer" target="_blank">http://public.kitware.com/mail<wbr>man/listinfo/paraview-develope<wbr>rs</a><br>
</div></div></blockquote></div><br></div></div>