From b63c76319fca75d3f1a8a85f4218703a82518295 Mon Sep 17 00:00:00 2001 From: Benjamin Berg Date: Tue, 12 May 2020 19:09:30 +0200 Subject: [PATCH] device: Make possible client vanished race testable using critical The tests cannot currently parse the logs of fprintd. This means we need to rely on fprintd aborting when a condition is hit that needs to be tested. This makes certain possible races when clients vanish testable. --- src/device.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/device.c b/src/device.c index 2591252..75d05fc 100644 --- a/src/device.c +++ b/src/device.c @@ -643,7 +643,7 @@ _fprint_device_client_vanished (GDBusConnection *connection, /* The session may have disappeared at this point if the device * was already closing. */ if (session && !fp_device_close_sync (priv->dev, NULL, &error)) - g_debug ("Error closing device after disconnect: %s", error->message); + g_critical ("Error closing device after disconnect: %s", error->message); session_data_set_new (priv, NULL, NULL); }