systemd/test/mkosi-check-and-shutdown.sh

#!/bin/bash -eux
# SPDX-License-Identifier: LGPL-2.1-or-later

systemctl --failed --no-legend | tee /failed-services

# Check that secure boot keys were properly enrolled.
if [[ -d /sys/firmware/efi/efivars/ ]]; then
    cmp /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c <(printf '\6\0\0\0\1')
    cmp /sys/firmware/efi/efivars/SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c <(printf '\6\0\0\0\0')
fi

# Exit with non-zero EC if the /failed-services file is not empty (we have -e set)
[[ ! -s /failed-services ]]

: >/testok
ci: check for failed services after boot This should, hopefully, catch issues like systemd/systemd#21671 automagically. 2021-12-08 21:31:25 +03:00			`#!/bin/bash -eux`
			`# SPDX-License-Identifier: LGPL-2.1-or-later`

			`systemctl --failed --no-legend \| tee /failed-services`

ci: Test with secure boot enabled under mkosi This gives us some nice test coverage for secure boot enrolling and the stub secure boot workound. The authenticated EFI variables are already created by mkosi, all we need to do is request secure boot to be used. 2023-01-31 20:53:28 +03:00			`# Check that secure boot keys were properly enrolled.`
			`if [[ -d /sys/firmware/efi/efivars/ ]]; then`
			`cmp /sys/firmware/efi/efivars/SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c <(printf '\6\0\0\0\1')`
			`cmp /sys/firmware/efi/efivars/SetupMode-8be4df61-93ca-11d2-aa0d-00e098032b8c <(printf '\6\0\0\0\0')`
			`fi`

ci: check for failed services after boot This should, hopefully, catch issues like systemd/systemd#21671 automagically. 2021-12-08 21:31:25 +03:00			`# Exit with non-zero EC if the /failed-services file is not empty (we have -e set)`
			`[[ ! -s /failed-services ]]`

			`: >/testok`