[vtkusers] Many VTK build tests fail when run from Jenkins/Bamboo or VNC display, even when DISPLAY is set to good opengl-enabled display

[John]

Thanks Ben,

I've submitted a run here:
https://open.cdash.org/buildSummary.php?buildid=5192358

The list of failing tests is here:
https://open.cdash.org/viewTest.php?onlyfailed&buildid=5192358

I'll keep my fingers Xed... it'd be great if someone with more knowledge
could take a look at the list of failing tests and spot something they
have in common!

John

----------


ps Re using VNC, for me it was an almost total failure, so i quickly
gave up and switched to sending the tests to my main Xorg/nvidia head.

Under vnc,the tests fail with an error message which says:

ERROR: In
/data-ssd/data/development/src/vtk/git/vtk-master/Rendering/OpenGL2/vtkOpenGLRenderWindow.cxx,
line 793
vtkXOpenGLRenderWindow (0x14251e0): GL version 2.1 with the gpu_shader4
extension is not supported by your graphics driver but is required for
the new OpenGL rendering backend. Please update your OpenGL driver. If
you are using Mesa please make sure you have version 10.6.5 or later and
make sure your driver in Mesa supports OpenGL 3.2.

It's odd, because it says i need mesa > 10.6.5 with GL version 2.1 but
I've got Mesa 17.2.4-2.fc27.x86_64, which provides "Max compat profile
version 2.1 and OpenGL > 3.2) and it still isn't happy. I think these
opengl features are just not supported on vnc, or not on my vnc
("llvmpipe" device, tigervnc server), or perhaps they are supported, but
i haven't worked out how to enable them. Maybe i just need to change the
"preferred profile, from "compat (0x2) to something newer.

(On VNC): glxinfo -B
name of display: :14.0
display: :14  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: VMware, Inc. (0xffffffff)
    Device: llvmpipe (LLVM 4.0, 256 bits) (0xffffffff)
    Version: 17.2.4
    Accelerated: no
    Video memory: 32113MB
    Unified memory: no
    Preferred profile: compat (0x2)
    Max core profile version: 0.0
    Max compat profile version: 2.1
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 2.0
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 4.0, 256 bits)
OpenGL version string: 2.1 Mesa 17.2.4
OpenGL shading language version string: 1.30

OpenGL ES profile version string: OpenGL ES 2.0 Mesa 17.2.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16



On 2017-12-23 2:20 AM, Ben Boeckel wrote:
> On Sat, Dec 23, 2017 at 00:13:50 +1030, John wrote:
>> Perhaps the reason these tests are failing is obvious to someone with a
>> more knowledge of the testing process?
> 
> I don't know how mcuh I'd be able to help, but if you could submit an
> experimental run to CDash and link to it, it'd make it easier to see
> what's common between the failing tests.
> 
> FWIW, we do have a few machines using VNC for their testing, but they're
> currently only testing ParaView. One is `megas` which tests Catalyst and
> the other is `pvbinsdash` which is working on the ParaView superbuild.
> Historically, `megas` also had VTK builds on it, but other than volume
> rendering tests (due to Fedora's Mesa not supporting floating point
> textures), some others were excluded mentioning "broken selection on
> VNC", "broken transparency on VNC(?)", and "broken stencil buffer on
> VNC(?)":
> 
>   - TestYoungsMaterialInterface
>   - TestWindowToImageTransparency
>   - rendererSource
> 
> --Ben
>