From 899dfbd45eccdd83ac895ccd3d2e12f367624b50 Mon Sep 17 00:00:00 2001 From: =?utf8?q?J=C3=B6rg=20Behrmann?= Date: Tue, 21 Jan 2025 15:57:19 +0100 Subject: [PATCH] tests: don't fail directory CI if lvm2-monitor.service fails MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit This service sometimes fails in CI for the arch:directory combination, e.g. 2025-01-21T12:07:33.4370559Z [ 14.125731] mkosi-check-and-shutdown.sh[419]: + systemctl --failed --no-legend 2025-01-21T12:07:33.4380022Z [ 14.126655] mkosi-check-and-shutdown.sh[420]: + tee /failed-services 2025-01-21T12:07:33.4714973Z [ 14.160448] mkosi-check-and-shutdown.sh[420]: ● lvm2-monitor.service not-found failed failed lvm2-monitor.service 2025-01-21T12:07:33.4751355Z [ 14.164135] mkosi-check-and-shutdown.sh[418]: + [[ ! -s /failed-services ]] This is the first time this appears in the partcular boot's logs and we always ignore it and carry on. Let's sidestep checking whether it is this particular error by masking the unit. A possible reason might be that it gets pulled in by udev if a test using LVM runs first. --- mkosi.postinst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/mkosi.postinst b/mkosi.postinst index d5bd991bd..3201196eb 100755 --- a/mkosi.postinst +++ b/mkosi.postinst @@ -16,3 +16,5 @@ mkosi-chroot \ --groups "$SUDO_GROUP",systemd-journal \ --shell /bin/bash \ mkosi + +systemctl --root="$BUILDROOT" mask lvm2-monitor.service -- 2.47.3