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 c2c3073ea80a039f6c0bd355b1b3b419bc16ffab..c32f7b9b5716a6a9c9eb0da6b0388304f6e51b22 100755 (executable)
--- 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