diff options
| author | Peter Hutterer <peter.hutterer@who-t.net> | 2017-03-14 11:23:55 +1000 |
|---|---|---|
| committer | Peter Hutterer <peter.hutterer@who-t.net> | 2017-03-14 12:33:15 +1000 |
| commit | c2b33f2a5383b85e3b0d4ce9d3c61ecded3bea9d (patch) | |
| tree | 1b63a746a8d2ec97531f20c851b48b3c93044007 | |
| parent | c05e92643c3a9d6aa192003a4c0ffe9cd42a597d (diff) | |
test: don't use the same mouse twice
No effect since we don't care about the mouse itself. But when running
on kernels without uinput's UI_GET_SYSNAME this can cause misdetection of
the uinput device and test case failures. Simply picking a differently named
device avoids that.
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
| -rw-r--r-- | test/test-touchpad.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/test/test-touchpad.c b/test/test-touchpad.c index 29039b3..c0de99b 100644 --- a/test/test-touchpad.c +++ b/test/test-touchpad.c @@ -4647,7 +4647,7 @@ START_TEST(touchpad_disabled_double_mouse) litest_assert_only_typed_events(li, LIBINPUT_EVENT_POINTER_MOTION); mouse1 = litest_add_device(li, LITEST_MOUSE); - mouse2 = litest_add_device(li, LITEST_MOUSE); + mouse2 = litest_add_device(li, LITEST_MOUSE_LOW_DPI); litest_assert_only_typed_events(li, LIBINPUT_EVENT_DEVICE_ADDED); litest_touch_down(dev, 0, 20, 30); @@ -4693,7 +4693,7 @@ START_TEST(touchpad_disabled_double_mouse_one_suspended) litest_assert_only_typed_events(li, LIBINPUT_EVENT_POINTER_MOTION); mouse1 = litest_add_device(li, LITEST_MOUSE); - mouse2 = litest_add_device(li, LITEST_MOUSE); + mouse2 = litest_add_device(li, LITEST_MOUSE_LOW_DPI); litest_assert_only_typed_events(li, LIBINPUT_EVENT_DEVICE_ADDED); /* Disable one external mouse -> don't expect touchpad events */ |