Package: autopkgtest Version: 5.24 Severity: serious Dear colleagues,
I was just trying to fix some package of mine and was running autopkgtest to see if the hang I see on ci.d.n is reproducible. However, autopkgtest has issues running reliably. Simon already reported this on IRC when releasing 5.24, but it's worse than I suspected. The following is seen, but not on every reboot. $ autopkgtest . --apt-upgrade --shell-fail -- lxc --sudo autopkgtest-unstable-amd64 [...] autopkgtest [21:45:36]: rebooting testbed after setup commands that affected boot autopkgtest-virt-lxc [21:45:43]: ERROR: Waiting for boot to finish failed autopkgtest-virt-lxc [21:45:43]: ERROR: Failed to connect to bus: No such file or directory <VirtSubproc>: failure: Waiting for boot to finish failed autopkgtest [21:45:45]: ERROR: testbed failure: unexpected eof from the testbed Paul -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages autopkgtest depends on: ii apt-utils 2.5.2 ii libdpkg-perl 1.21.9 ii procps 2:3.3.17-7+b1 ii python3 3.10.5-3 ii python3-debian 0.1.46 Versions of packages autopkgtest recommends: ii autodep8 0.26 ii fakeroot 1.29-1 Versions of packages autopkgtest suggests: pn docker.io <none> pn fakemachine <none> ii lxc 1:5.0.1-1 pn lxd <none> ii ovmf 2022.05-2 pn ovmf-ia32 <none> pn podman <none> ii python3-distro-info 1.1 pn qemu-efi-aarch64 <none> pn qemu-efi-arm <none> pn qemu-system <none> ii qemu-utils 1:7.0+dfsg-7+b1 ii schroot 1.6.12-2 ii util-linux 2.38.1-1 ii vmdb2 0.26-1 -- no debconf information
