Package: debci-worker Version: 2.1 Severity: important User: de...@kali.org Usertags: origin-kali
On our setup, we use the qemu backend on a big machine with lots of RAM and CPU, so we have many workers running concurrently. With a backlog, there's often no point in time where the qemu image is not used at all. This means that /usr/share/debci/bin/debci-setup will never get the exclusive lock that it is trying to get... and thus the daily cron will get stuck indefinitely. They will even accumulate days after days... The cron should fail it's not able to get the lock it wants in a reasonable timeframe. Given the time it can take until the lock is acquired (some tests take multiple hours), the script should likely be moved out of /etc/cron.daily/. There should also be an option to stop the worker at the start so that the update can happen immediately (and they should be restarted at the end if they were running before). -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debci-worker depends on: ii autodep8 0.18 ii autopkgtest 5.10 pn debci <none> ii init-system-helpers 1.57 ii schroot 1.6.10-6+b1 debci-worker recommends no packages. debci-worker suggests no packages.
