- Mar 28, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This triggers on Fedora 30, even though skip skip the tools options test when running under valgrind. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Not sure how this ever worked correctly: a process terminated by a signal has the negative signo as return code. This would apply to every debug-events and debug-gui test because they have to get killed by a signal. This failed occasionally, presumably a race with the GTK startup/signal handler/whatever. Fix this by a) sending SIGQUIT because that won't get handled by the tools and b) prending that if we get a -SIGQUIT exit code, everything is fine. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Pass arguments we don't handle directly through to the unittest module. This way we can filter tests with -k testname etc. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 27, 2019
-
-
Peter Hutterer authored
Still not great and probably makes any professional designer's eyes bleed, but at least it's more readable now. Changes: - spacing after param name so they don't cuddle up with the description - color changes and background image removals to drop the doxygen default look - font size changes to not make things overrun - font family change to make the function prototypes readable Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 25, 2019
-
-
Peter Hutterer authored
Two resource leaks, one uninitialized variable. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 22, 2019
-
-
Peter Hutterer authored
Now that we're emulating everything correctly, let's mark it as proper touch device. Two test cases need to be excluded: - double-down triggers an assert in the test device because this isn't possible this way with protocol A devices - the axisrange warning test can't be triggered, mtdev clips those axes Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This device mostly behaved like a normal touch device except for SYN_MT_REPORT. Switch it to behave like a real protocol A device and adjust the test accordingly. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This is so we can tell litest to create the device anyway, useful for when all we have to do in the custom create is allocate some memory. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Removed with 27188228 but we still had the meson define being set. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
When running the test-suite, don't install our rules for device groups and model quirks - they're expected to be present already. Plus, since we copy them from the meson build dir, we don't have those files available anyway. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 21, 2019
-
-
Konstantin Kharlamov authored
All "goto err" resides after fd have been properly initialized. Fixes "Comparison is always true because fd >= 0." warning by LGTM. Signed-off-by: Konstantin Kharlamov <Hi-Angel@yandex.ru>
-
Konstantin Kharlamov authored
Fixes "Comparison is always false because rc >= 0." warning by LGTM. Signed-off-by: Konstantin Kharlamov <Hi-Angel@yandex.ru>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
The button up debouncing states mirror the button down states with the addition of the spurious debouncing states. Rename the states to better show this symmetry.
-
- Mar 18, 2019
-
-
Paolo Giangrandi authored
Multitap sequences (more than 2 taps) had a 180ms timer set only on press, not on release. New taps within those 180ms could either trigger multitap+drag or another multitap (for N+1 taps), resetting the timer on press once again. If no new tap appears within those 180ms, the sequence was considered complete. This behavior differed from regular taps: for the very first tap of a sequence the timer was set both on touch and on release. The multitap timing caused misdetection of triple-tap-and-drag sequences as the timer was hit frequently. Some of those were correctly detected, others as tripletap only. Changing the timer to be set on press **and** release gives us a more lenient timeout. 180ms for tap-and-drag and 180ms for the next tap down after release. This was also the behavior for the xorg synaptics driver. Note that quadruple-tap-and-drag didn't suffer from this because the timeout resulted in double-tap + double-tap-and-drag. Which has the same user-visible effect.
-
- Mar 17, 2019
-
-
- Mar 15, 2019
-
-
Peter Hutterer authored
Now that we're providing the test suite as installed option, distributions will likely include it as a test package. valgrind is only used for the meson-specifc test setup. So let's make it optional. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 14, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Available as 'libinput test-suite'. This also renames the bit in the build directory now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This allows us to run the test suite runner against the installed system rather than always using the build tree quirks. The actual option will be removed in a future commit, it is just here for commit consistency and testing. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
We want to use this from the tests as well soon, so let's move it to a more generic location. This also changes the API to be slightly more sensible, a free() is the same cost (and safer) than passing a static buffer in and hoping we didn't get the size wrong. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
All the bits that test for utility functions to work correctly can be run separately from the main test suite (which tests devices and libinput in general). These bits here are the ones that test the code itself and aren't reliant on anything else. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
No functional changes Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
It's a one-liner, we don't need this as a separate file. Plus, this makes the test suite runner less dependent on the build directory. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
These don't need to be in the libinput config.h Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 12, 2019
-
-
Peter Hutterer authored
We don't want to valgrind through python... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
If more than 255 tests fail, we're returning an exit code outside of the POSIX standard. This only takes effect for -j1, where we fork off we only ever have a failed value of 1 anyway. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Running the test suite runner is good, but not sufficient, a full ninja test is required to get the full coverage. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
With meson this is now in the build directory Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 06, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 04, 2019
-
-
Peter Hutterer authored
Draw a second smaller scroll bar that moves with every discrete step. For that to work, we have to accumulate the value from the normal scroll events until we get the first discrete one, then move up. The value per discrete event changes depending on the click wheel angle, so we can't just use discrete on its own if we want the two scroll bars aligned. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-