test: fix the lookup for the timer offset warnings
authorPeter Hutterer <peter.hutterer@who-t.net>
Thu, 16 Apr 2020 00:58:00 +0000 (10:58 +1000)
committerPeter Hutterer <peter.hutterer@who-t.net>
Wed, 13 May 2020 06:21:27 +0000 (06:21 +0000)
This was changed in 5e25bdfb0374bf7f9a6b5fc887e81d6a0b492f70 but the litest
message lookup wasn't changed. Let's do that now and change to a generic
wording we can re-use for other messages.

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

index 391c8e9eb6103b17ef68245478bb3fc7391016cb..182094cbf1d28e74773c3e9b7c130ad0431231fc 100644 (file)
@@ -678,7 +678,7 @@ litest_log_handler(struct libinput *libinput,
                 * short, don't abort if during a valgrind run we get a
                 * negative offset */
                if ((!RUNNING_ON_VALGRIND && !in_debugger) ||
-                   !strstr(format, "offset negative"))
+                   !strstr(format, "your system is too slow"))
                litest_abort_msg("libinput bug triggered, aborting.\n");
        }