https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/ Issue: app-emulation/libvirt-9.3.0 fails tests (MUSL-SYSTEM). Discovered on: amd64 (internal ref: tinderbox_musl) NOTE: (MUSL-SYSTEM) in the summary means that bug was found on a machine that runs MUSL libc but this bug MAY or MAY NOT BE related to musl.
Created attachment 861536 [details] build.log.xz build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
Created attachment 861537 [details] 1-testlog.txt.xz 1-testlog.txt (compressed because it exceeds attachment limit, use 'xzless' to read it)
Error(s) that match a know pattern: 2) QEMU vhost-user precedence test ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/vhost-user/60-gpu.json: No such file or directory 50/141 virpcitest FAIL 0.07s killed by signal 11 SIGSEGV 50/141 virpcitest FAIL 0.07s killed by signal 11 SIGSEGV 10) QEMU FW precedence test ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 1082) QEMU XML-2-ARGV aarch64-virt-headless.aarch64-latest ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 1088) QEMU XML-2-ARGV aarch64-virt-graphics.aarch64-latest ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 1094) QEMU XML-2-ARGV vhost-user-vga.x86_64-latest ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/vhost-user/60-gpu.json: No such file or directory 1095) QEMU XML-2-ARGV vhost-user-gpu-secondary.x86_64-latest ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/vhost-user/60-gpu.json: No such file or directory 1118) QEMU XML-2-ARGV hvf-aarch64-virt-headless.aarch64-latest ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 18) qemu_7.0.0-q35.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 19) qemu_7.0.0-tcg.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 20) qemu_7.0.0.ppc64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 2023-05-11 15:25:25.827+0000: 3703: error : qemuBuildFileList:61 : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 2023-05-11 15:25:25.828+0000: 3703: error : qemuBuildFileList:61 : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 2023-05-11 15:25:25.837+0000: 3703: error : qemuBuildFileList:61 : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 2023-05-11 15:25:25.847+0000: 3703: error : qemuBuildFileList:61 : Unable to access /usr/share/qemu/vhost-user/60-gpu.json: No such file or directory 2023-05-11 15:25:25.849+0000: 3703: error : qemuBuildFileList:61 : Unable to access /usr/share/qemu/vhost-user/60-gpu.json: No such file or directory 2023-05-11 15:25:25.901+0000: 3703: error : qemuBuildFileList:61 : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 21) qemu_7.0.0.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 22) qemu_7.0.0-virt.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 23) qemu_7.0.0-hvf.aarch64+hvf ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 24) qemu_6.2.0.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 25) qemu_6.2.0-q35.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 26) qemu_6.2.0-tcg.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 27) qemu_6.2.0.ppc64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 28) qemu_6.2.0.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 29) qemu_6.2.0-virt.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 30) qemu_6.1.0.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 31) qemu_6.1.0-q35.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 32) qemu_6.1.0-tcg.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 33) qemu_6.0.0.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 34) qemu_6.0.0-q35.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 35) qemu_6.0.0-tcg.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 36) qemu_6.0.0.s390x ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 37) qemu_6.0.0.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 38) qemu_6.0.0-virt.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 39) qemu_5.2.0.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 40) qemu_5.2.0-q35.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 41) qemu_5.2.0-tcg.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 42) qemu_5.2.0.s390x ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 43) qemu_5.2.0-virt.riscv64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 44) qemu_5.2.0-tcg-virt.riscv64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 45) qemu_5.2.0.ppc64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 46) qemu_5.2.0.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 47) qemu_5.2.0-virt.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 48) qemu_5.1.0.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 49) qemu_5.1.0-q35.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 50) qemu_5.1.0-tcg.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 51) qemu_5.1.0.sparc ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 52) qemu_5.0.0.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 53) qemu_5.0.0-q35.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 54) qemu_5.0.0-tcg.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 55) qemu_5.0.0-virt.riscv64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 56) qemu_5.0.0-tcg-virt.riscv64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 57) qemu_5.0.0.ppc64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 58) qemu_5.0.0.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 59) qemu_5.0.0-virt.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 60) qemu_4.2.0.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 61) qemu_4.2.0-q35.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 62) qemu_4.2.0-tcg.x86_64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 63) qemu_4.2.0.s390x ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 64) qemu_4.2.0.ppc64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 65) qemu_4.2.0.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory 66) qemu_4.2.0-virt.aarch64 ... libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory FAILED Program augparse found: NO Program flake8 found: NO Program iscsiadm found: NO Program mdevctl found: NO Program mm-ctl found: NO Program ovs-vsctl found: NO Program passt found: NO Program pdwtags found: NO Program showmount found: NO Program slirp-helper found: NO Run-time dependency devmapper found: NO (tried pkgconfig and cmake) Run-time dependency fuse3 found: NO (tried pkgconfig and cmake) Run-time dependency libiscsi found: NO (tried pkgconfig and cmake) Run-time dependency parallels-sdk found: NO (tried pkgconfig and cmake) libvirt: Cgroup error : Failed to create v1 controller cpu for group: No such file or directory libvirt: Cgroup error : Path '/fakedevdir0/bla/fasl' is not accessible: No such file or directory libvirt: QEMU Driver error : Unable to access /usr/share/qemu/firmware/70-aavmf.json: No such file or directory libvirt: Security Driver error : unable to stat: /dev/HostVG/QEMUGuest1: No such file or directory libvirt: Security Driver error : unable to stat: /var/lib/libvirt/images/guest.qcow2: No such file or directory libvirt: Security Driver error : unable to stat: /var/lib/libvirt/images/test.img: No such file or directory 10) Detect cgroup mounts for no-cgroups ... libvirt: Cgroup error : internal error: no cgroup backend available
Thanks for the report. This looks like a genuine libvirt bug. Let me take a closer look.
Patch posted on the list: https://listman.redhat.com/archives/libvir-list/2023-May/239866.html Long story short, libvirt provides an alternative implementation for stat()-like functions for unit tests, that redirect paths back into repository (so that tests do not depend on the actual host). But musl-1.2.4 removed some symbols rendering our stat mocking ineffective. Hence those failures in test suite.
Fixed upstream as: https://gitlab.com/libvirt/libvirt/-/commit/a091edf9db5d6e949190d9ea6ad384570c30def0 Since this is reproducible only with yet unstable version of musl, I think it's okay if this fix is picked up by rebase of app-emulation/libvirt (the next release is planned at the end of May/beginning of June).
(In reply to Michal Prívozník from comment #6) > Fixed upstream as: > > https://gitlab.com/libvirt/libvirt/-/commit/ > a091edf9db5d6e949190d9ea6ad384570c30def0 > > Since this is reproducible only with yet unstable version of musl, I think > it's okay if this fix is picked up by rebase of app-emulation/libvirt (the > next release is planned at the end of May/beginning of June). That's no problem, thank you! I will say: I hadn't thought about that specific issue from Alpine reverting it. Alpine is the "default" musl CI that people use. Very, very few distros will be doing CI with a non-Alpine musl CI image. This is really both shooting themselves in the foot as well as other musl distros :(
Meant to say: > I will say: I hadn't thought about that specific issue from Alpine reverting > it. Alpine is the "default" musl CI that people use. Very, very few projects > will be doing CI with a non-Alpine musl CI image. This is really both > shooting themselves in the foot as well as other musl distros :(
