From 71c15cdbeaf6e58fa57e6c3f769e906ec0727c3b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Sat, 4 Apr 2026 11:24:45 +0200 Subject: [PATCH] TEST-74-AUX-UTILS: check for failed units after capsule test TEST-74-AUX-UTILS has a number of subtests. test/units/TEST-74-AUX-UTILS.capsule.sh runs first and starts and stops capsule@foobar.service. Looking at the test, the unit is cleanly stopped. But later test/units/TEST-74-AUX-UTILS.machine-id-setup.sh tests for failed units. capsule@foobar.service is listed as failed, causing the second subtest to fail. Add the same test in test/units/TEST-74-AUX-UTILS.capsule.sh to see if the failed test really originates from there. --- test/units/TEST-74-AUX-UTILS.capsule.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/test/units/TEST-74-AUX-UTILS.capsule.sh b/test/units/TEST-74-AUX-UTILS.capsule.sh index c2c3073ea8..c32f7b9b57 100755 --- a/test/units/TEST-74-AUX-UTILS.capsule.sh +++ b/test/units/TEST-74-AUX-UTILS.capsule.sh @@ -58,3 +58,8 @@ systemctl clean capsule@foobar.service --what=all (! test -f /run/capsules/foobar ) (! test -f /var/lib/capsules/foobar ) (! id -u c-foobar ) + +systemctl status capsule@foobar.service || : + +systemctl --state=failed --no-legend --no-pager | tee /failed +test ! -s /failed