From: Zbigniew Jędrzejewski-Szmek Date: Sat, 4 Apr 2026 09:24:45 +0000 (+0200) Subject: TEST-74-AUX-UTILS: check for failed units after capsule test X-Git-Tag: v261-rc1~610 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=71c15cdbeaf6e58fa57e6c3f769e906ec0727c3b;p=thirdparty%2Fsystemd.git 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. --- diff --git a/test/units/TEST-74-AUX-UTILS.capsule.sh b/test/units/TEST-74-AUX-UTILS.capsule.sh index c2c3073ea80..c32f7b9b571 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