test: use motion events to check the "system is too slow" message
authorPeter Hutterer <peter.hutterer@who-t.net>
Fri, 12 Feb 2021 00:24:43 +0000 (10:24 +1000)
committerPeter Hutterer <peter.hutterer@who-t.net>
Fri, 12 Feb 2021 01:05:38 +0000 (11:05 +1000)
Using buttons for this test can trigger debounce warnings instead (in
addition?) to the warning we actually check for. Let's use motion events
instead and double the loop while we're at it so we have double the chance of
triggering at least one warning.

Fixes #574 for unknown reasons

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
test/test-misc.c

index 4a946d4..c3523bf 100644 (file)
@@ -715,10 +715,9 @@ START_TEST(timer_delay_bug_warning)
        user_data->private = &warning_triggered;
        libinput_log_set_handler(li, timer_delay_warning);
 
-       for (int i = 0; i < 10; i++) {
-               litest_button_click(dev, BTN_LEFT, true);
-               libinput_dispatch(li);
-               litest_button_click(dev, BTN_LEFT, false);
+       for (int i = 0; i < 20; i++) {
+               litest_event(dev, EV_REL, REL_X, -1);
+               litest_event(dev, EV_SYN, SYN_REPORT, 0);
                msleep(11);
                libinput_dispatch(li);
        }