QA (public) » openQA Project (public) » openQA Tests (public)

as sle15 will most likely also make use of wayland

That would surprise me as YaST does not run on Wayland (at all - root applications are explicitly disallowed
to connect to the compositor and/or XWayland)

Anyway:

Generally I see these issues with Wayland (compositor independant):

• Most compositors require proper DRM support -> Cirrus won't work anymore
• Different appearance of native Wayland applications (different render paths) -> New needles required

Depending on the display manager and compositor there's also the issue that the VT the compositor
runs on is not well defined. Most display managers stay active in the background when starting
a wayland session (gdm, and sddm do, not sure about other wayland compatible ones) and so VT7
is not available.
Additionally, the display manager allocates the VT so the allocation is not the same on all desktops.
In fact, sddm asks the kernel for the next unallocated one so the VT number is depending on the previous
test modules. Without consoletest_setup for instance kwin_wayland is started on tty2, with on tty3.
It might be an option to define a minimum base VT in coordination with the other desktops for easier QA
testing to get a deterministic VT number.

As most "x11" parts of openQA also apply to wayland, the test group should probably be renamed to
"graphical", same for the console.

I do not know about issues with GNOME on Wayland as so far it's apparently not possible to
start a wayland session in QEMU at all (https://lists.opensuse.org/opensuse-factory/2017-07/msg00709.html).

openQA won't Load the lastgood snapshot when a test module failed in wayland testing.

e.g. kde-wayland@64bit_virtio (with QEMUVGA=virtio) failed at:
https://openqa.opensuse.org/tests/520926#step/khelpcenter/120
The failed module terminated the whole job, all the test modules after khelpcenter.pm were skipped.

Expected Results:

kde@64bit failed at ooffice.pm:
https://openqa.opensuse.org/tests/520585#step/khelpcenter/1
But openQA will load the lastgood VM for the rest test modules.

I can reproduce this on my local instance:
http://10.67.17.30/tests/1980

$rpm -qa | grep openQA

openQA-client-4.5.1509097496.8b8e8e20-12.1.noarch
openQA-4.5.1509097496.8b8e8e20-12.1.noarch
openQA-worker-4.5.1509097496.8b8e8e20-12.1.noarch
openQA-common-4.5.1509097496.8b8e8e20-12.1.noarch

It works fine on:
http://10.67.17.21/tests/118

openQA-common-4.4.1500993922.f0db2597-95.1.noarch
openQA-worker-4.4.1500993922.f0db2597-95.1.noarch
openQA-client-4.4.1500993922.f0db2597-95.1.noarch
openQA-4.4.1500993922.f0db2597-95.1.noarch

qkzhu wrote:

openQA won't Load the lastgood snapshot when a test module failed in wayland testing.

e.g. kde-wayland@64bit_virtio (with QEMUVGA=virtio) failed at:
https://openqa.opensuse.org/tests/520926#step/khelpcenter/120
The failed module terminated the whole job, all the test modules after khelpcenter.pm were skipped.

QEMU only supports savestating of virtio-gpu in version >= 2.10 (IIRC). The version on o3 (except on aarch64 workers) is too old.