Discrepancies in xts results between master and xwayland-24.1
Preparing the branching of xwayland-25.1
(#1793 !1852), I ran the XTS test suite on the current xwayland-24.1 branch and from xwayland-25.1 from !1852 to detect possible regressions.
Xwayland get started with:
Xwayland -decorate -ac +byteswappedclients -noreset
And xts-run
is started on the display created by the above command.
As it turns out, the results are not identical.
Attaching the results:
Tests that differ are:
- xts5/Xlib13/XGrabButton (9/39): FAIL
- xts5/Xlib13/XGrabButton (10/39): FAIL
- xts5/Xlib13/XGrabButton (11/39): FAIL
- xts5/Xlib13/XGrabButton (12/39): FAIL
- xts5/Xlib13/XGrabButton (14/39): FAIL
- xts5/Xlib13/XGrabButton (16/39): FAIL
- xts5/Xlib13/XGrabButton (17/39): UNRESOLVED
- xts5/Xlib13/XGrabButton (19/39): FAIL
- xts5/Xlib13/XGrabButton (20/39): UNRESOLVED
- xts5/Xlib13/XGrabButton (21/39): FAIL
- xts5/Xlib13/XGrabButton (22/39): FAIL
- xts5/Xlib13/XGrabButton (23/39): FAIL
- xts5/Xlib13/XGrabButton (24/39): FAIL
- xts5/Xlib13/XGrabButton (25/39): FAIL
- xts5/Xlib13/XGrabButton (27/39): UNRESOLVED
- xts5/Xlib13/XGrabKey (1/16): FAIL
- xts5/Xlib13/XGrabKey (2/16): UNRESOLVED
- xts5/Xlib13/XGrabKey (3/16): UNRESOLVED
- xts5/Xlib13/XGrabKey (4/16): UNRESOLVED
- xts5/Xlib13/XGrabKey (5/16): UNRESOLVED
- xts5/Xlib13/XGrabKey (6/16): FAIL
- xts5/Xlib13/XGrabKey (7/16): FAIL
- xts5/Xlib13/XUngrabButton (1/6): UNRESOLVED
- xts5/Xlib13/XUngrabButton (4/6): FAIL
- xts5/Xlib13/XUngrabKey (1/7): UNRESOLVED
- xts5/Xlib13/XUngrabKey (2/7): UNRESOLVED
- xts5/XI/GrabDeviceButton (7/21): FAIL
- xts5/XI/GrabDeviceButton (10/21): FAIL
- xts5/XI/GrabDeviceKey (10/21): FAIL
And there is also a test which now is PASS
(previously FAIL
):
- xts5/XI/XGetDeviceModifierMapping (2/4): PASS
I am tempted to consider those are regressions, but it requires more investigation, so filing this as a heads up.