Hello, guys.
I have a one question about the libinput API.
I want to get device's bustype to know how this device is connected.
But there is no thie API and that API is supported only in libevdev.
But other APIs to get device information are supported(abstracted) in
libinput.
We can't call system() in the signal handler but we are allowed to fork. Do
that, update the hwdb and immediately exit the child again.
Signed-off-by: Peter Hutterer
---
test/litest.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/test/litest.c
We only have a single test runner now, so no need to restrict it.
Signed-off-by: Peter Hutterer
---
test/Makefile.am | 2 --
1 file changed, 2 deletions(-)
diff --git a/test/Makefile.am b/test/Makefile.am
index 32e379a..23a4bc8 100644
--- a/test/Makefile.am
+++
Don't fork by default if we're in gdb.
Note that is_debugger_attached() is now inside #ifndef LITEST_NO_MAIN, gdb for
the litest selftest will now require a manual CK_FORK=no.
Signed-off-by: Peter Hutterer
---
doc/test-suite.dox | 3 ++-
test/litest.c | 71
We're grouping by test suites, so split up the suites a bit further. The tap
tests all have timeouts and thus take forever, splitting them across multiple
forks means we can finish the test suite quicker.
Signed-off-by: Peter Hutterer
---
test/touchpad-tap.c | 84
Running tests in parallel virtually guarantees a different device is added in
between. What we're testing here is that the device comes back and the
original ref doesn't send events, so a false test failure would still indicate
a bug anyway.
Signed-off-by: Peter Hutterer
Not needed anymore, we only have one process creating the udev rules.
This reverts commit 030ec053fbbc17f9bd0a3a8c6003318864986de7.
---
configure.ac | 3 ---
test/litest.c | 63 ---
2 files changed, 66 deletions(-)
diff --git
Likely testing a specific set of tests, possibly in gdb. So don't parallelize.
Signed-off-by: Peter Hutterer
---
test/litest.c | 16
1 file changed, 16 insertions(+)
diff --git a/test/litest.c b/test/litest.c
index 5a8498f..902543d 100644
---
Signed-off-by: Peter Hutterer
---
test/litest.c | 35 ++-
1 file changed, 34 insertions(+), 1 deletion(-)
diff --git a/test/litest.c b/test/litest.c
index 7c18568..492aa3a 100644
--- a/test/litest.c
+++ b/test/litest.c
@@ -34,6 +34,7 @@
Add a make-like -j/--jobs option to split the number of parallel test
processes. Defaults to 8 if not specified, future patches will default this to
1 for special cases where filters are specified or gdb is detected.
Each subprocess overwrites argv[0] to be easier identifiable in the ps
output
The udev hwdb takes about 200ms and we still trigger it on each device. The
udev rules don't actually change after compiling, so simply create them
once and remove them after the test run.
For multiple test binaries this needed to be synchronized (which is hard),
hence the previous merge into a
Call it a libinput-test-suite-runner, in subsequent patches we'll handle doing
parallel tests ourselves instead of relying on automake features.
Signed-off-by: Peter Hutterer
---
doc/test-suite.dox | 14 +++
test/Makefile.am| 104
With parallel builds the valgrind test run would run at the same time as the
normal run, the test suite isn't designed for that.
Signed-off-by: Peter Hutterer
---
test/Makefile.am | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test/Makefile.am
Easier to clean up than knowing all the destination paths we'll install.
Only affects global udev rules so far.
Signed-off-by: Peter Hutterer
---
test/litest.c | 79 ---
1 file changed, 54 insertions(+), 25
A current test run takes anywhere north of 30 minutes on a good machine.
Much of that time is spent either rebuilding the hwdb or just waiting for
various timeouts.
We run the tests in serial to avoid interference between the various udev
rules. Running the current set in parallel has some
On Tue, Jul 26, 2016 at 04:09:48PM -0500, Yong Bakos wrote:
> From: Yong Bakos
>
> From: Bill Spitzak
>
> Scanner has been generating the doxygen group label "foo_iface" for all
> *_add_listener functions, and the label "iface_foo" everywhere else.
On 01.08.2016 19:17, Armin Krezović wrote:
> This patch makes the compositor user data a structure
> which can be expanded with new fields when necessary.
>
> v2:
>
> Don't export to_wet_compositor
>
> Signed-off-by: Armin Krezović
> ---
> compositor/main.c | 20
This uses container_of instead of explicit cast to retrieve
backend and output objects from generic weston_backend and
weston_output pointers.
Signed-off-by: Armin Krezović
---
libweston/compositor-x11.c | 28
1 file changed, 20
This uses container_of instead of explicit cast to retrieve
backend and output objects from generic weston_backend and
weston_output pointers.
Signed-off-by: Armin Krezović
---
libweston/compositor-rdp.c | 16 ++--
1 file changed, 14 insertions(+), 2
On Mon, Aug 01, 2016 at 12:48:21PM +1000, Peter Hutterer wrote:
> On Fri, Jul 29, 2016 at 09:43:59AM -0700, Bryce Harrington wrote:
> > Adds a safe strtol helper function, modeled loosely after Wayland
> > scanner's strtouint. This encapsulates the various quirks of strtol
> > behavior, and
20 matches
Mail list logo