[Webkit-unassigned] [Bug 165232] New: [GTK][Wayland] Allow running the layout tests under a native Wayland environment.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=165232

            Bug ID: 165232
           Summary: [GTK][Wayland] Allow running the layout tests under a
                    native Wayland environment.
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Tools / Tests
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: clopez at igalia.com
                CC: lforschler at apple.com

In bug 156716 we implemented support for running the layout tests under a virtualized wayland environment (weston running on top of Xvfb).

We now want to allow running the tests in a native wayland environment (the user's wayland session). 

This feature is going to be used on the wayland test bot that we are going to deploy ASAP. We think running the tests on wayland with a hardware-backed OpenGL implementation makes more sense than use mesa's llvmpipe software rasterizer.

For Xorg, we do this by exporting the environment variable USE_NATIVE_XDISPLAY=1

I propose to do something similar here.

So:

* if you pass the flag --wayland to run-webkit-tests a wayland (virtualized) environment will be used
* if you pass the flag --wayland and also export USE_NATIVE_WAYLAND=1 then your native wayland environment will be used

I think this is consistent with the current behaviour for X11:

* if you don't pass any special flag, the default X11 (virtualized xvfb) will be used
* if you don't pass any special flag and you export USE_NATIVE_XDISPLAY=1 env var, then your native X11 session will be used.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161201/1f4fbddd/attachment.html>