You are not logged in.

#1 2020-01-14 03:29:58

RamenDevourer
Member
Registered: 2019-04-25
Posts: 4
Website

libfprint-git installation fails on X1 Carbon Gen 7

The libfprint-git package recently got updated with the Synaptics Inc, drivers (06cb:00bd) for my Thinkpad X1 Carbon Gen 7.
Yet, when I try to install it, the following occurs:

==> Starting check()...
ninja: Entering directory `/home/master/.cache/yay/libfprint-git/src/build'
ninja: no work to do.
1/7 libfprint / virtual-image               SKIP     0.01 s
2/7 libfprint:drivers / elan                FAIL     0.07 s (exit status 1)
3/7 libfprint:drivers / vfs5011             FAIL     0.07 s (exit status 1)
4/7 libfprint:drivers / synaptics           FAIL     0.07 s (exit status 1)
5/7 libfprint:unit-tests / fpi-device       OK       0.23 s
6/7 libfprint:unit-tests / fpi-ssm          OK       1.08 s
7/7 libfprint:unit-tests / fpi-assembling   OK       0.33 s

Ok:                    3
Expected Fail:         0
Fail:                  3
Unexpected Pass:       0
Skipped:               1
Timeout:               0

Full log written to /home/master/.cache/yay/libfprint-git/src/build/meson-logs/testlog.txt
==> ERROR: A failure occurred in check().
    Aborting...
Error making: libfprint-git

Here is the output of the log file mentionned in the installation ($HOME/.cache/yay/libfprint-git/src/build/meson-logs/testlogs.txt):

Log of Meson test suite run on 2020-01-13T22:20:54.371519

Inherited environment: SHELL='/usr/bin/zsh' WINDOWID='81788934' LESS='-R' XDG_SESSION_PATH='/org/freedesktop/DisplayManager/Session1' READER='/usr/bin/zathura' I3SOCK='/run/user/1000/i3/ipc-socket.686' LESS_TERMCAP_se='[0m' LESS_TERMCAP_so='[01;44;33m' TEXTDOMAINDIR='/usr/share/locale' GRDB='dropbox://default@/git-private' DESKTOP_SESSION='/usr/share/xsessions/i3' EDITOR='/usr/bin/nvim' GTK_MODULES='canberra-gtk-module' XDG_SEAT='seat0' PWD='/home/master/.cache/yay/libfprint-git/src' SOURCE_DATE_EPOCH='1578972041' XDG_SESSION_DESKTOP='i3' LOGNAME='master' QT_QPA_PLATFORMTHEME='qt5ct' XDG_SESSION_TYPE='x11' CXXFLAGS='-march=x86-64 -mtune=generic -O2 -pipe -fno-plt' XAUTHORITY='/home/master/.Xauthority' DESKTOP_STARTUP_ID='i3/st/686-8-workbook_TIME2446019' TERMINAL='st' COMMAND_MODE='legacy' GTK2_RC_FILES='/home/master/.gtkrc-2.0' LDFLAGS='-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now' HOME='/home/master' LANG='en_CA.UTF-8' XDG_CURRENT_DESKTOP='i3' KEYTIMEOUT='1' XDG_SEAT_PATH='/org/freedesktop/DisplayManager/Seat0' CPPFLAGS='-D_FORTIFY_SOURCE=2' XDG_SESSION_CLASS='user' TERM='st-256color' LESS_TERMCAP_mb='[1;31m' LESS_TERMCAP_me='[0m' LESS_TERMCAP_md='[1;36m' USER='master' DISPLAY=':0' SHLVL='2' LESS_TERMCAP_ue='[0m' LESS_TERMCAP_us='[1;32m' XDG_VTNR='1' XDG_SESSION_ID='2' BIB='/home/master/Dropbox/A/Scholar/All/References' XDG_RUNTIME_DIR='/run/user/1000' REFERBIB='/home/master/Dropbox/A/Scholar/All/References/bibliography.refer' CHOST='x86_64-pc-linux-gnu' BROWSER='firefox' PATH=':/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl:/home/master/.scripts/tmux:/home/master/.scripts/i3cmds:/home/master/.scripts/polybar:/home/master/.scripts/cron:/home/master/.scripts/tools:/home/master/.scripts/colorschemes:/home/master/.scripts/fun:/home/master/.scripts/::/root/.local/bin:/home/master/.local/bin' CFLAGS='-march=x86-64 -mtune=generic -O2 -pipe -fno-plt' DBUS_SESSION_BUS_ADDRESS='unix:path=/run/user/1000/bus' MAIL='/var/spool/mail/master' OLDPWD='/home/master/.cache/yay/libfprint-git/src' GOPATH='/home/master/.go' TEXTDOMAIN='pacman-scripts' _='/usr/bin/meson' 

1/7 libfprint / virtual-image               SKIP     0.01 s 

--- command ---
03:20:54 /usr/bin/sh -c exit 77
-------

2/7 libfprint:drivers / elan                FAIL     0.07 s (exit status 1)

--- command ---
03:20:54 FP_DRIVERS_WHITELIST='elan' NO_AT_BRIDGE='1' LD_LIBRARY_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' MESON_SOURCE_ROOT='/home/master/.cache/yay/libfprint-git/src/libfprint' G_MESSAGES_DEBUG='all' FP_DEVICE_EMULATION='1' G_DEBUG='fatal-warnings' GI_TYPELIB_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' /home/master/.cache/yay/libfprint-git/src/libfprint/tests/umockdev-test.py /home/master/.cache/yay/libfprint-git/src/libfprint/tests/elan
--- stderr ---
Traceback (most recent call last):
  File "/home/master/.cache/yay/libfprint-git/src/libfprint/tests/umockdev-test.py", line 15, in <module>
    umockdev_version = subprocess.check_output(['umockdev-run', '--version'])
  File "/usr/lib/python3.8/subprocess.py", line 411, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.8/subprocess.py", line 489, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: 'umockdev-run'
-------

3/7 libfprint:drivers / vfs5011             FAIL     0.07 s (exit status 1)

--- command ---
03:20:54 NO_AT_BRIDGE='1' LD_LIBRARY_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' MESON_SOURCE_ROOT='/home/master/.cache/yay/libfprint-git/src/libfprint' G_MESSAGES_DEBUG='all' FP_DEVICE_EMULATION='1' G_DEBUG='fatal-warnings' GI_TYPELIB_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' FP_DRIVERS_WHITELIST='vfs5011' /home/master/.cache/yay/libfprint-git/src/libfprint/tests/umockdev-test.py /home/master/.cache/yay/libfprint-git/src/libfprint/tests/vfs5011
--- stderr ---
Traceback (most recent call last):
  File "/home/master/.cache/yay/libfprint-git/src/libfprint/tests/umockdev-test.py", line 15, in <module>
    umockdev_version = subprocess.check_output(['umockdev-run', '--version'])
  File "/usr/lib/python3.8/subprocess.py", line 411, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.8/subprocess.py", line 489, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: 'umockdev-run'
-------

4/7 libfprint:drivers / synaptics           FAIL     0.07 s (exit status 1)

--- command ---
03:20:54 NO_AT_BRIDGE='1' LD_LIBRARY_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' MESON_SOURCE_ROOT='/home/master/.cache/yay/libfprint-git/src/libfprint' G_MESSAGES_DEBUG='all' FP_DEVICE_EMULATION='1' FP_DRIVERS_WHITELIST='synaptics' G_DEBUG='fatal-warnings' GI_TYPELIB_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' /home/master/.cache/yay/libfprint-git/src/libfprint/tests/umockdev-test.py /home/master/.cache/yay/libfprint-git/src/libfprint/tests/synaptics
--- stderr ---
Traceback (most recent call last):
  File "/home/master/.cache/yay/libfprint-git/src/libfprint/tests/umockdev-test.py", line 15, in <module>
    umockdev_version = subprocess.check_output(['umockdev-run', '--version'])
  File "/usr/lib/python3.8/subprocess.py", line 411, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.8/subprocess.py", line 489, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/usr/lib/python3.8/subprocess.py", line 854, in __init__
    self._execute_child(args, executable, preexec_fn, close_fds,
  File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: 'umockdev-run'
-------

5/7 libfprint:unit-tests / fpi-device       OK       0.23 s 

--- command ---
03:20:54 FP_DRIVERS_WHITELIST='virtual_image' NO_AT_BRIDGE='1' LD_LIBRARY_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' MESON_SOURCE_ROOT='/home/master/.cache/yay/libfprint-git/src/libfprint' G_MESSAGES_DEBUG='all' FP_DEVICE_EMULATION='1' G_DEBUG='fatal-warnings' GI_TYPELIB_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' /home/master/.cache/yay/libfprint-git/src/libfprint/tests/test-runner.sh tests/test-fpi-device
--- stdout ---
# random seed: R02S5b727b1859a54caa68f40d7e8dffcf36
1..60
# Start of driver tests
ok 1 /driver/get_driver
ok 2 /driver/get_device_id
ok 3 /driver/get_name
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 3 in idle!
ok 4 /driver/is_open
ok 5 /driver/get_nr_enroll_stages
ok 6 /driver/set_nr_enroll_stages
ok 7 /driver/supports_identify
ok 8 /driver/supports_capture
ok 9 /driver/has_storage
ok 10 /driver/do_not_support_identify
ok 11 /driver/do_not_support_capture
ok 12 /driver/has_not_storage
ok 13 /driver/get_usb_device
ok 14 /driver/get_virtual_env
ok 15 /driver/get_driver_data
# libfprint-device-DEBUG: Device reported probe completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported probe completion
# libfprint-device-DEBUG: Completing action 1 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 1 in idle!
ok 16 /driver/probe
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 3 in idle!
ok 17 /driver/open
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 3 in idle!
ok 18 /driver/close
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported enroll completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported enroll completion
# libfprint-device-DEBUG: Completing action 4 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 4 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 3 in idle!
ok 19 /driver/enroll
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported verify result
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.395: Device reported verify completion
# libfprint-device-DEBUG: Completing action 5 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Completing action 5 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Completing action 3 in idle!
ok 20 /driver/verify
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported identify result
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Device reported identify completion
# libfprint-device-DEBUG: Completing action 6 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Completing action 6 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.396: Completing action 3 in idle!
ok 21 /driver/identify
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported capture completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Device reported capture completion
# libfprint-device-DEBUG: Completing action 7 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Completing action 7 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Completing action 3 in idle!
ok 22 /driver/capture
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported listing completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Device reported listing completion
# libfprint-device-DEBUG: Completing action 8 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Completing action 8 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.397: Completing action 3 in idle!
ok 23 /driver/list
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported deletion completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Device reported deletion completion
# libfprint-device-DEBUG: Completing action 9 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Completing action 9 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Completing action 3 in idle!
ok 24 /driver/delete
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Completing action 2 in idle!
# libfprint-device-DEBUG: Idle cancelling on ongoing operation!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.398: Idle cancelling on ongoing operation!
# libfprint-device-DEBUG: Device reported deletion completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.498: Device reported deletion completion
# libfprint-device-DEBUG: Completing action 9 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.498: Completing action 9 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.498: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.498: Completing action 3 in idle!
ok 25 /driver/cancel
ok 26 /driver/get_current_action
ok 27 /driver/timeout
ok 28 /driver/error_types
ok 29 /driver/retry_error_types
# Start of get_scan_type tests
ok 30 /driver/get_scan_type/press
ok 31 /driver/get_scan_type/swipe
# End of get_scan_type tests
# Start of set_scan_type tests
ok 32 /driver/set_scan_type/press
ok 33 /driver/set_scan_type/swipe
# End of set_scan_type tests
# Start of open tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Completing action 2 in idle!
ok 34 /driver/open/error
# End of open tests
# Start of close tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Completing action 3 in idle!
ok 35 /driver/close/error
# End of close tests
# Start of enroll tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported enroll completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Device reported enroll completion
# libfprint-device-DEBUG: Completing action 4 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Completing action 4 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Completing action 3 in idle!
ok 36 /driver/enroll/error
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.548: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported enroll progress, reported 464586449 of 60183025 have been completed
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported enroll progress, reported 464586449 of 60183025 have been completed
# libfprint-device-DEBUG: Device reported enroll progress, reported 1773863677 of 60183025 have been completed
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported enroll progress, reported 1773863677 of 60183025 have been completed
# libfprint-device-DEBUG: Device reported enroll progress, reported 1162302936 of 60183025 have been completed
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported enroll progress, reported 1162302936 of 60183025 have been completed
# libfprint-device-DEBUG: Device reported enroll completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported enroll completion
# libfprint-device-DEBUG: Completing action 4 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 4 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 3 in idle!
ok 37 /driver/enroll/progress
# End of enroll tests
# Start of verify tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported verify result
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported verify completion
# libfprint-device-DEBUG: Completing action 5 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 5 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 3 in idle!
ok 38 /driver/verify/fail
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported verify result
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported verify result
# libfprint-device-DEBUG: Device reported verify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported verify completion
# libfprint-device-DEBUG: Completing action 5 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 5 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 3 in idle!
ok 39 /driver/verify/retry
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported verify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported verify completion
# libfprint-device-DEBUG: Completing action 5 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 5 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 3 in idle!
ok 40 /driver/verify/error
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported verify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported verify completion
# libfprint-device-DEBUG: Completing action 5 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 5 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 3 in idle!
ok 41 /driver/verify/not_reported
# End of verify tests
# Start of identify tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.549: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported identify result
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Device reported identify completion
# libfprint-device-DEBUG: Completing action 6 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Completing action 6 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Completing action 3 in idle!
ok 42 /driver/identify/fail
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported identify result
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Device reported identify result
# libfprint-device-DEBUG: Device reported identify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Device reported identify completion
# libfprint-device-DEBUG: Completing action 6 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Completing action 6 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Completing action 3 in idle!
ok 43 /driver/identify/retry
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.550: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported identify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.551: Device reported identify completion
# libfprint-device-DEBUG: Completing action 6 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.551: Completing action 6 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.551: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.551: Completing action 3 in idle!
ok 44 /driver/identify/error
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported identify completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported identify completion
# libfprint-device-DEBUG: Completing action 6 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 6 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 45 /driver/identify/not_reported
# End of identify tests
# Start of capture tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported capture completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported capture completion
# libfprint-device-DEBUG: Completing action 7 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 7 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 46 /driver/capture/error
# End of capture tests
# Start of list tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported listing completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported listing completion
# libfprint-device-DEBUG: Completing action 8 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 8 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 47 /driver/list/error
# End of list tests
# Start of delete tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported deletion completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported deletion completion
# libfprint-device-DEBUG: Completing action 9 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 9 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 48 /driver/delete/error
# End of delete tests
# Start of cancel tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported deletion completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported deletion completion
# libfprint-device-DEBUG: Completing action 9 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 9 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 49 /driver/cancel/fail
# End of cancel tests
# Start of get_current_action tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 50 /driver/get_current_action/open
# End of get_current_action tests
# Start of get_cancellable tests
ok 51 /driver/get_cancellable/error
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 52 /driver/get_cancellable/open
# Start of open tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 53 /driver/get_cancellable/open/fail
# End of open tests
# End of get_cancellable tests
# Start of action_is_cancelled tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 2 in idle!
# libfprint-device-DEBUG: Device reported close completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Device reported close completion
# libfprint-device-DEBUG: Completing action 3 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.552: Completing action 3 in idle!
ok 54 /driver/action_is_cancelled/open
ok 55 /driver/action_is_cancelled/error
# End of action_is_cancelled tests
# Start of complete_action tests
# Start of all tests
ok 56 /driver/complete_action/all/error
# End of all tests
# End of complete_action tests
# Start of action_error tests
ok 57 /driver/action_error/error
# libfprint-device-DEBUG: Device reported generic error during action; action was: 2
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.553: Device reported generic error during action; action was: 2
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.553: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.553: Completing action 2 in idle!
ok 58 /driver/action_error/open
# Start of fail tests
# libfprint-device-DEBUG: Device reported open completion
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.553: Device reported open completion
# libfprint-device-DEBUG: Completing action 2 in idle!
(tests/test-fpi-device:336244): libfprint-device-DEBUG: 22:20:54.553: Completing action 2 in idle!
ok 59 /driver/action_error/fail/open
# End of fail tests
# End of action_error tests
# Start of timeout tests
ok 60 /driver/timeout/cancelled
# End of timeout tests
# End of driver tests
-------

6/7 libfprint:unit-tests / fpi-ssm          OK       1.08 s 

--- command ---
03:20:54 FP_DRIVERS_WHITELIST='virtual_image' NO_AT_BRIDGE='1' LD_LIBRARY_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' MESON_SOURCE_ROOT='/home/master/.cache/yay/libfprint-git/src/libfprint' G_MESSAGES_DEBUG='all' FP_DEVICE_EMULATION='1' G_DEBUG='fatal-warnings' GI_TYPELIB_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' /home/master/.cache/yay/libfprint-git/src/libfprint/tests/test-runner.sh tests/test-fpi-ssm
--- stdout ---
# random seed: R02S0a7fbeb364fb258acc1054f93e9bd28e
1..43
# Start of ssm tests
ok 1 /ssm/new
ok 2 /ssm/set_data
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM entering state 0
ok 3 /ssm/start
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 4 /ssm/next
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 5 /ssm/jump_to_state
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 6 /ssm/mark_completed
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.391: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
ok 7 /ssm/mark_failed
# Start of new tests
ok 8 /ssm/new/full
ok 9 /ssm/new/no_handler
ok 10 /ssm/new/wrong_states
# End of new tests
# Start of set_data tests
ok 11 /ssm/set_data/cleanup
# End of set_data tests
# Start of start tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully
ok 12 /ssm/start/single
# End of start tests
# Start of next tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM entering state 1
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM entering state 3
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 13 /ssm/next/complete
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 14 /ssm/next/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.392: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 15 /ssm/next/with_delayed
# End of next tests
# Start of jump_to_state tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.492: [fake_test_dev] FPI_TEST_SSM entering state 2
ok 16 /ssm/jump_to_state/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.492: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.492: [fake_test_dev] FPI_TEST_SSM entering state 2
ok 17 /ssm/jump_to_state/with_delayed
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.592: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.592: [fake_test_dev] FPI_TEST_SSM entering state 3
ok 18 /ssm/jump_to_state/last
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.592: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.592: [fake_test_dev] FPI_TEST_SSM entering state 14
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.592: [fake_test_dev] FPI_TEST_SSM entering state -10
ok 19 /ssm/jump_to_state/wrong
# End of jump_to_state tests
# Start of mark_completed tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.592: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 20 /ssm/mark_completed/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.592: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.592: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 21 /ssm/mark_completed/with_delayed
# End of mark_completed tests
# Start of mark_failed tests
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.693: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.693: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
ok 22 /ssm/mark_failed/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.693: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.693: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The driver encountered a protocol error with the device.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.693: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
ok 23 /ssm/mark_failed/with_delayed
# End of mark_failed tests
# Start of delayed tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.793: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.803: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 24 /ssm/delayed/next
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.803: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.813: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.823: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 25 /ssm/delayed/jump_to_state
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.824: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.834: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 26 /ssm/delayed/mark_completed
# Start of next tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.834: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.834: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 27 /ssm/delayed/next/cancel
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.934: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.934: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.934: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 28 /ssm/delayed/next/cancellable
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.945: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 29 /ssm/delayed/next/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.945: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.955: [fake_test_dev] FPI_TEST_SSM entering state 1
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.965: [fake_test_dev] FPI_TEST_SSM entering state 2
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.975: [fake_test_dev] FPI_TEST_SSM entering state 3
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.986: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 30 /ssm/delayed/next/complete
# End of next tests
# Start of jump_to_state tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.986: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:54.986: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 31 /ssm/delayed/jump_to_state/cancel
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.086: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.086: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.086: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 32 /ssm/delayed/jump_to_state/cancellable
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.096: [fake_test_dev] FPI_TEST_SSM entering state 2
ok 33 /ssm/delayed/jump_to_state/not_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.096: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.107: [fake_test_dev] FPI_TEST_SSM entering state 3
ok 34 /ssm/delayed/jump_to_state/last
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.107: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.117: [fake_test_dev] FPI_TEST_SSM entering state 14
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.127: [fake_test_dev] FPI_TEST_SSM entering state -10
ok 35 /ssm/delayed/jump_to_state/wrong
# End of jump_to_state tests
# Start of mark_completed tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.127: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.127: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 36 /ssm/delayed/mark_completed/cancel
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.228: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.228: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.228: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 37 /ssm/delayed/mark_completed/cancellable
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.238: [fake_test_dev] FPI_TEST_SSM completed successfully
ok 38 /ssm/delayed/mark_completed/not_started
# End of mark_completed tests
# Start of cancel tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
ok 39 /ssm/delayed/cancel/error
# End of cancel tests
# End of delayed tests
# Start of subssm tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 40 /ssm/subssm/start
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] SSM FPI_TEST_SUB_SSM failed in state 0 with error: The device is still busy with another operation, please try again later.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SUB_SSM completed with error: The device is still busy with another operation, please try again later.
# libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: The device is still busy with another operation, please try again later.
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later.
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later.
ok 41 /ssm/subssm/mark_failed
# Start of start tests
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.329: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 42 /ssm/subssm/start/with_started
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.330: [fake_test_dev] FPI_TEST_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.330: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.430: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
# libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
(tests/test-fpi-ssm:336242): libfprint-SSM-DEBUG: 22:20:55.430: [fake_test_dev] FPI_TEST_SSM entering state 1
ok 43 /ssm/subssm/start/with_delayed
# End of start tests
# End of subssm tests
# End of ssm tests
-------

7/7 libfprint:unit-tests / fpi-assembling   OK       0.33 s 

--- command ---
03:20:54 FP_DRIVERS_WHITELIST='virtual_image' NO_AT_BRIDGE='1' LD_LIBRARY_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' MESON_SOURCE_ROOT='/home/master/.cache/yay/libfprint-git/src/libfprint' G_MESSAGES_DEBUG='all' FP_DEVICE_EMULATION='1' G_DEBUG='fatal-warnings' GI_TYPELIB_PATH='/home/master/.cache/yay/libfprint-git/src/build/libfprint' /home/master/.cache/yay/libfprint-git/src/libfprint/tests/test-runner.sh tests/test-fpi-assembling
--- stdout ---
# random seed: R02Sd12d7b9744a8689afc8f539b5889160f
1..1
# Start of assembling tests
# libfprint-assembling-DEBUG: calc delta completed in 0.084754 secs
(tests/test-fpi-assembling:336245): libfprint-assembling-DEBUG: 22:20:54.484: calc delta completed in 0.084754 secs
# libfprint-assembling-DEBUG: calc delta completed in 0.083689 secs
(tests/test-fpi-assembling:336245): libfprint-assembling-DEBUG: 22:20:54.567: calc delta completed in 0.083689 secs
# libfprint-assembling-DEBUG: errors: 0 rev: 130848
(tests/test-fpi-assembling:336245): libfprint-assembling-DEBUG: 22:20:54.567: errors: 0 rev: 130848
# libfprint-assembling-DEBUG: calc delta completed in 0.093096 secs
(tests/test-fpi-assembling:336245): libfprint-assembling-DEBUG: 22:20:54.660: calc delta completed in 0.093096 secs
# libfprint-assembling-DEBUG: height is 310
(tests/test-fpi-assembling:336245): libfprint-assembling-DEBUG: 22:20:54.660: height is 310
ok 1 /assembling/frames
# End of assembling tests
-------


Ok:                    3
Expected Fail:         0
Fail:                  3
Unexpected Pass:       0
Skipped:               1
Timeout:               0

How could I fix the installation?

Offline

#2 2020-01-14 09:16:28

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 8,393

Re: libfprint-git installation fails on X1 Carbon Gen 7

If you don't care about the unit test working skip the check function, either edit the pkgbuild and remove the check function or pass --nocheck to makepkg. Though the fact that the unit test fails might point to problematic code.

 yay -S --mflags --nocheck libfprint-git

should work.

Offline

Board footer

Powered by FluxBB