Heads-up people - seems the build workers are on strike.

When checking a scheduled build -> the following msg appears:

waiting for 8 compliant workers (1 of them down) (7 of them bad)


And when a package does try to build - this is a snippet from the logs:

[ 0s] booting kvm...
[ 0s] ### VM INTERACTION START ###
[ 0s] Using UART console
[ 0s] /usr/bin/qemu-kvm -nodefaults -no-reboot -nographic -vga none -cpu host -M pc,accel=kvm,usb=off,dump-guest-core=off,vmport=off -sandbox on -bios /usr/share/qemu/qboot.rom -object rng-random,filename=/dev/random,id=rng0 -device virtio-rng-pci,rng=rng0 -runas qemu -mem-prealloc -mem-path /dev/hugetlbfs -net none -kernel /boot/vmlinuz -initrd /boot/initrd -append root=/dev/sda rootfstype=ext4 rootflags=noatime no-kvmclock mitigations=off elevator=noop nmi_watchdog=0 rw rd.driver.pre=binfmt_misc oops=panic panic=1 quiet console=ttyS0 init=/.build/build -m 5741 -drive file=/var/cache/obs/worker/root_1/root,format=raw,if=none,id=disk,cache=unsafe -device ide-hd,drive=disk,serial=0 -drive file=/var/cache/obs/worker/root_1/swap,format=raw,if=none,id=swap,cache=unsafe -device ide-hd,drive=swap,serial=1 -serial stdio -chardev socket,id=monitor,server=on,wait=off,path=/var/cache/obs/worker/root_1/root.qemu/monitor -mon chardev=monitor,mode=readline -smp 1
[ 0s] qemu_madvise: Invalid argument
[ 0s] madvise doesn't support MADV_DONTDUMP, but dump_guest_core=off specified [ 2s] [-1;-1f[ OK ] Started Show Plymouth Boot Screen. [ 2s] [ OK ] Started Forward Password R…s to Plymouth Directory Watch.
[ 2s] [ OK ] Reached target Path Units.
[ 2s] [ OK ] Reached target Basic System.
[ 2s] [ OK ] Found device QEMU_HARDDISK.
[ 2s] [ OK ] Reached target Initrd Root Device.
[ 129s] [ 128.405390] dracut-initqueue[344]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 129s] [ 128.408320] dracut-initqueue[344]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fsda.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 129s] [ 128.408351] dracut-initqueue[344]: [ -e "/dev/sda" ]
[ 129s] [ 128.408373] dracut-initqueue[344]: fi"
[ 129s] [ 128.413368] dracut-initqueue[344]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fsystem\x2froot.sh: "[ -e "/dev/system/root" ]" [ 129s] [ 128.415950] dracut-initqueue[344]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fsystem\x2fswap.sh: "[ -e "/dev/system/swap" ]" [ 129s] [ 128.418729] dracut-initqueue[344]: Warning: dracut-initqueue: starting timeout scripts [ 130s] [ 128.953074] dracut-initqueue[344]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 130s] [ 128.955260] dracut-initqueue[344]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fsda.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 130s] [ 128.955296] dracut-initqueue[344]: [ -e "/dev/sda" ]
[ 130s] [ 128.955307] dracut-initqueue[344]: fi"
[ 130s] [ 128.959502] dracut-initqueue[344]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fsystem\x2froot.sh: "[ -e "/dev/system/root" ]" [ 130s] [ 128.961718] dracut-initqueue[344]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fsystem\x2fswap.sh: "[ -e "/dev/system/swap" ]" [ 130s] [ 128.964119] dracut-initqueue[344]: Warning: dracut-initqueue: starting timeout scripts [ 130s] [ 129.489156] dracut-initqueue[344]: Warning: dracut-initqueue: timeout, still waiting for following initqueue hooks: [ 130s] [ 129.491159] dracut-initqueue[344]: Warning: /lib/dracut/hooks/initqueue/finished/devexists-\x2fdev\x2fsda.sh: "if ! grep -q After=remote-fs-pre.target /run/systemd/generator/systemd-cryptsetup@*.service 2>/dev/null; then
[ 130s] [ 129.491192] dracut-initqueue[344]: [ -e "/dev/sda" ]
[ 130s] [ 129.491204] dracut-initqueue[344]: fi"

This goes on and on until

[ 193s] Generating "/run/initramfs/rdsosreport.txt"
[ 193s]
[ 193s]
[ 193s] Entering emergency mode. Exit the shell to continue.
[ 193s] Type "journalctl" to view system logs.
[ 193s] You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
[ 193s] after mounting them and attach it to a bug report.
[ 193s]
[ 193s]
[ 193s] Give root password for maintenance

/B



_______________________________________________
Packman mailing list
[email protected]
https://lists.links2linux.de/cgi-bin/mailman/listinfo/packman

Antwort per Email an