[PATCH v3 2/6] user32: Implement GetRegisteredRawInputDevices.

Francois Gouget fgouget at free.fr
Fri Jul 3 08:32:36 CDT 2020

On Fri, 3 Jul 2020, Rémi Bernon wrote:
> Ah indeed, I thought I could add more arguments to run them all.
> The monitor test causes a Xephyr segmentation fault locally, but the msg test
> seems to run fine. I wonder if it could be snowballing from the monitor test.

I don't see X error messages in the "full task log". But if X segfaulted 
directly that would probably not be visible there.

I never tested it but if X segfaults I suspect we'd get back to the 
chooser which should reconnect the default user after the standard 
timeout (<30 seconds) and the tests are likely to continue running in 
the meantime. It's possible they could be stuck while X is restarting 
which could explain the string of timeouts.

It may be possible to test for this condition by starting an independent 
windows process displaying a window in an early test 
(CreateProcess("clock.exe")?) and checking the final screenshot to see 
if that window is still there.

Francois Gouget <fgouget at free.fr>              http://fgouget.free.fr/
                         "Utilisateur" (nom commun) :
        Mot utilisé par les informaticiens en lieu et place d'"idiot".

More information about the wine-devel mailing list