delta/libevdev.git/test/test-libevdev-init.c, branch libevdev-1.4.6

cosmetic: fix a couple of duplicate/missing empty lines

2015-03-03T22:41:33+00:00

Signed-off-by: Peter Hutterer

test: add test for clock id setting on an invalid device

2014-11-17T23:05:14+00:00

Signed-off-by: Peter Hutterer

test: add test case for grab calls on invalid devices

2014-11-17T23:04:03+00:00

Signed-off-by: Peter Hutterer

Add per-device log handlers

2014-06-05T05:16:06+00:00

The global log handler isn't a good choice for a low-level library. In the
caser of the X server, both evdev and synaptics are now using the libevdev but
are loaded from the same server process. Thus, there's only one log handler,
but evdev and synaptics don't talk to each other (a bit childish, I know).

Add a per-device log handler that overrides the global log handler, and fall
back to the global log handler if no device log handler is set. The log
macros take care of that automatically, especially as we can't do per-device
log handlers for the uinput code.

Note that we use the same struct for the global and device logging, so in each
instance one of the two function pointers is NULL. Suicide triggers are in
place in case we mess that up.

This also makes libevdev_new_from_fd() a bit less useful since we can't set
the log handler beforehand.

Signed-off-by: Peter Hutterer 
Reviewed-by: David Herrmann

test: restore default log priority after tests

2014-04-07T23:01:50+00:00

Signed-off-by: Peter Hutterer

test: remove checks for test device creation failure

2014-04-02T01:35:56+00:00

test_create_... fails on a non-zero return code anyway

Signed-off-by: Peter Hutterer

test: whitespace fixes (newlines)

2014-03-05T09:16:08+00:00

Signed-off-by: Peter Hutterer

Actually filter by log priority

2014-02-12T22:07:30+00:00

If a message is higher than the current priority, filter it. And add a few
tests that the priority is handled the way it should.

Signed-off-by: Peter Hutterer 
Reviewed-by: David Herrmann

test: abort on unexpected log messages

2014-01-21T23:14:40+00:00

Add two log functions, one that aborts on a received message. We know when we
expect to receive an error, so anytime this happens unexpectedly should
terminate the test.

And for those tests do issue a log message, let them ignore it and don't
print anything.

Signed-off-by: Peter Hutterer

Fix wrong libevdev clock test

2013-10-31T01:23:13+00:00

We can rely on CLOCK_MONOTONIC and CLOCK_REALTIME to be different at any
time. However, this does not apply to the ms/us/ns parts of the current
time. Both may be in sync regarding the current micro-seconds state. So
remove the wrong clock us-comparison.

I was able to trigger this on my machine. Chances that both are in sync
are very low so I assume my RTC only provides low granularity and thus
both clocks are sync during boot for higher granularity.

Signed-off-by: David Herrmann 
Reviewed-by: Peter Hutterer 
Signed-off-by: Peter Hutterer