27351): libfprint-synaptics-DEBUG: 22:34:18.428: Finger is now off the sensor
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.429: Received message with 0 sequence number 0x91, ignoring!
(process:27351): libfprint-SSM-DEBUG: 22:34:18.430: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.441: interrupt transfer done
(process:27351): libfprint-SSM-DEBUG: 22:34:18.443: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
(process:27351): libfprint-SSM-DEBUG: 22:34:18.464: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
(process:27351): libfprint-SSM-DEBUG: 22:34:18.465: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:27351): libfprint-SSM-DEBUG: 22:34:18.466: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.497: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 79.430000
(process:27351): libfprint-device-DEBUG: 22:34:18.498: Device reported verify result
(process:27351): libfprint-device-DEBUG: 22:34:18.500: Device reported verify completion
(process:27351): libfprint-SSM-DEBUG: 22:34:18.516: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:27351): libfprint-device-DEBUG: 22:34:18.517: Completing action 5 in idle!
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.586: data is 0x2afe3e72a0
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.587: 70324395273: ../libfprint/drivers/synaptics/synaptics.c:943
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.588: sequence number is 5
(process:27351): libfprint-SSM-DEBUG: 22:34:18.589: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:27351): libfprint-SSM-DEBUG: 22:34:18.604: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.606: Successfully deleted enrolled user
(process:27351): libfprint-device-DEBUG: 22:34:18.607: Device reported deletion completion
(process:27351): libfprint-SSM-DEBUG: 22:34:18.623: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:27351): libfprint-device-DEBUG: 22:34:18.625: Completing action 9 in idle!
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.628: 70324436462: ../libfprint/drivers/synaptics/synaptics.c:1167
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.629: sequence number is 6
(process:27351): libfprint-SSM-DEBUG: 22:34:18.630: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
(process:27351): libfprint-SSM-DEBUG: 22:34:18.650: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
(process:27351): libfprint-synaptics-DEBUG: 22:34:18.695: Fingerprint sensor ready to be powered down
(process:27351): libfprint-device-DEBUG: 22:34:18.697: Device reported close completion
(process:27351): libfprint-SSM-DEBUG: 22:34:18.707: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
(process:27351): libfprint-device-DEBUG: 22:34:18.709: Completing action 3 in idle!
** (umockdev-run:27350): DEBUG: 22:34:18.765: umockdev-run.vala:61: umockdev-run: caught signal 15, propagating to child
** (umockdev-run:27350): DEBUG: 22:34:18.769: umockdev.vala:100: Removing test bed /tmp/umockdev.KDQPL0
-------
Full log written to /builddir/build/BUILD/libfprint-v1.90.1/riscv64-redhat-linux-gnu/meson-logs/testlog.txt
error: Bad exit status from /var/tmp/rpm-tmp.qtdA0Z (%check)
RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.qtdA0Z (%check)
Child return code was: 1
EXCEPTION: [Error()]
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/mockbuild/trace_decorator.py", line 95, in trace
    result = func(*args, **kw)
  File "/usr/lib/python3.8/site-packages/mockbuild/util.py", line 746, in do_with_status
    raise exception.Error("Command failed: \n # %s\n%s" % (command, output), child.returncode)
mockbuild.exception.Error: Command failed: 
 # bash --login -c /usr/bin/rpmbuild -bb --target riscv64 --nodeps /builddir/build/SPECS/libfprint.spec