test: use a plain libinput context for the log priority check
authorPeter Hutterer <peter.hutterer@who-t.net>
Tue, 19 Oct 2021 03:01:23 +0000 (13:01 +1000)
committerPeter Hutterer <peter.hutterer@who-t.net>
Tue, 19 Oct 2021 03:05:00 +0000 (13:05 +1000)
Don't use the litest wrapper context here, it changes log priority if
the test suite is run with --verbose, causing the test to fail.

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

index 346955e..0f344f5 100644 (file)
@@ -47,17 +47,34 @@ simple_log_handler(struct libinput *libinput,
        litest_assert_notnull(format);
 }
 
+
+static int open_restricted(const char *path, int flags, void *data)
+{
+       int fd;
+       fd = open(path, flags);
+       return fd < 0 ? -errno : fd;
+}
+static void close_restricted(int fd, void *data)
+{
+       close(fd);
+}
+
+static const struct libinput_interface simple_interface = {
+       .open_restricted = open_restricted,
+       .close_restricted = close_restricted,
+};
+
 START_TEST(log_default_priority)
 {
        enum libinput_log_priority pri;
        struct libinput *li;
 
-       li = litest_create_context();
+       li = libinput_path_create_context(&simple_interface, NULL);
        pri = libinput_log_get_priority(li);
 
        ck_assert_int_eq(pri, LIBINPUT_LOG_PRIORITY_ERROR);
 
-       litest_destroy_context(li);
+       libinput_unref(li);
 }
 END_TEST