I bisected a problem on qemuarm64 on arm64 build host when using clang as compiler. It seems to be related systemd bump to 251.4 commit 96e409c10f4a44433f2bbe55f9fb6981ea413a5e (HEAD) Author: Khem Raj <raj.khem@gmail.com> Date: Mon Aug 15 20:35:51 2022 -0700 systemd: Upgrade to 251.4 and fix build with binutils 2.39 The mount.h conflict patch is now upstream so drop it. Additionally this version fixes build with binutils-2.39 [1] [1] https://github.com/systemd/systemd-stable/commit/8a6f966be404897b5333c218701965ac3b5a0806 (From OE-Core rev: d43ec090ceb2bf0016a065103a4c34d0c43cb906) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> A workaround is to use TOOLCHAIN = "gcc" for now. Its a regression since 251.3 worked alright With this version we see RESULTS - systemd.SystemdBasicTests.test_systemd_failed: FAILED (122.64s) RESULTS - weston.WestonTest.test_weston_can_initialize_new_wayland_compositor: FAILED (0.18s) RESULTS - weston.WestonTest.test_weston_running: FAILED (0.37s) RESULTS - weston.WestonTest.test_weston_supports_xwayland: FAILED (0.19s) .... AssertionError: False is not true : Timed out waiting for systemd to settle: UNIT LOAD ACTIVE SUB DESCRIPTION dev-vda.device loaded activating tentative /dev/vda .... It seems its not able to settle the virtual disk device which leads to these issues.
We think this is resolved since it hasn't been happening.
(In reply to comment #1) > We think this is resolved since it hasn't been happening. In meta-clang we have forced it to use gcc see https://github.com/kraj/meta-clang/blob/master/recipes-core/systemd/systemd_%25.bbappend#L3 have you tried by unbolting this workaround ?
Finally, I can see that systemd upgrade to 252.4 has fixed this problem/regression