fprintd/tests
Marco Trevisan (Treviño) 0994cc314e main: Ensure that a gcov flush happens on SIGTERM
When coverage is enabled fprintd test won't generate any .gcda file and so
apparently no data, this happens because gcov doesn't handle properly the
process termination when SIGTERM is used, and so when in fprintd.py we
terminate the process no coverage data is reported.

To avoid this, quit the main loop cleanly on SIGTERM, so that we will exit
from the main function cleanly, making libc to perform a gcov flush when we
exit the program.
2020-02-05 16:45:57 +01:00
..
dbusmock tests: Fix num-enroll-stages signature in dbusmock template 2020-02-04 15:38:17 +01:00
pam tests: Increase debugging level for PAM tests 2020-02-05 15:25:35 +01:00
prints tests: Add test prints from libfprint 2019-12-03 17:08:03 +01:00
fprintd.py main: Ensure that a gcov flush happens on SIGTERM 2020-02-05 16:45:57 +01:00
Makefile.am tests: Add test for the PAM module 2020-01-22 15:34:02 +01:00
meson.build tests: Increase debugging for daemon tests 2020-02-05 15:25:35 +01:00
test_fprintd_utils.py test_fprintd_utils: Support running under valgrind 2020-02-04 15:39:01 +01:00