Package: autopkgtest Version: 5.42 Severity: normal Dear Maintainer,
I'm observing that the podman package keeps failing with 'tmpfail' result: https://ci.debian.net/packages/p/podman/testing/amd64/ Note that the package is configured to use qemu instead of debci. This is holding up migration to testing. I've been able to reproduce the symptom locally. Using pystack, I was able to determine where the process hangs: (pystack) siretart@x1:/tmp $ pystack remote 32478 Traceback for thread 32481 (runcmd) [] (most recent call last): (Python) File "/usr/lib/python3.12/threading.py", line 1032, in _bootstrap self._bootstrap_inner() (Python) File "/usr/lib/python3.12/threading.py", line 1075, in _bootstrap_inner self.run() (Python) File "/usr/lib/python3.12/threading.py", line 1012, in run self._target(*self._args, **self._kwargs) (Python) File "/tmp/autopkgtest-qemu.ai0h585s/runcmd", line 37, in shovel time.sleep(0.01) Traceback for thread 32480 (runcmd) [] (most recent call last): (Python) File "/usr/lib/python3.12/threading.py", line 1032, in _bootstrap self._bootstrap_inner() (Python) File "/usr/lib/python3.12/threading.py", line 1075, in _bootstrap_inner self.run() (Python) File "/usr/lib/python3.12/threading.py", line 1012, in run self._target(*self._args, **self._kwargs) (Python) File "/tmp/autopkgtest-qemu.ai0h585s/runcmd", line 37, in shovel time.sleep(0.01) Traceback for thread 32478 (runcmd) [] (most recent call last): (Python) File "/tmp/autopkgtest-qemu.ai0h585s/runcmd", line 79, in <module> time.sleep(0.2) Apparently, the runcmd script is looking for the 'exit' file to be created. This led me to looking at the job directory: siretart@x1:/tmp/autopkgtest-qemu.tvv_adh3 $ find . -ls 9699 0 drwxr-xr-x 3 siretart siretart 180 Nov 25 07:23 . 9700 0 drwxrwxrwt 3 siretart siretart 120 Nov 25 07:24 ./shared 9707 0 -rw-r--r-- 1 siretart siretart 0 Nov 25 07:23 ./shared/done_shared 9715 4 -rw-r--r-- 1 siretart siretart 5 Nov 25 07:23 ./shared/normal_user 9848 0 drwxr-xr-x 2 siretart siretart 120 Nov 25 07:24 ./shared/job.kdzgmbyv 9849 288 -rw-rw-r-- 1 siretart siretart 293351 Nov 25 07:24 ./shared/job.kdzgmbyv/stdout 9850 440 -rw-rw-r-- 1 siretart siretart 450097 Nov 25 07:24 ./shared/job.kdzgmbyv/stderr 9851 0 -rwxrwxr-x 1 siretart siretart 0 Nov 25 07:23 ./shared/job.kdzgmbyv/stdin 9852 4 -rw-rw-r-- 1 siretart siretart 1 Nov 25 07:23 ./shared/job.kdzgmbyv/stdin_eof 9855 4 -rw-r--r-- 1 siretart siretart 2 Nov 25 07:24 ./shared/exit.tmp 9702 0 srwxrwxr-x 1 siretart siretart 0 Nov 25 07:22 ./monitor 9703 0 srwxrwxr-x 1 siretart siretart 0 Nov 25 07:22 ./hvc0 9704 0 srwxrwxr-x 1 siretart siretart 0 Nov 25 07:22 ./hvc1 9705 0 srwxrwxr-x 1 siretart siretart 0 Nov 25 07:22 ./ttyS0 9706 0 srwxrwxr-x 1 siretart siretart 0 Nov 25 07:22 ./ttyS1 9708 4 -rwxr-xr-x 1 siretart siretart 3252 Nov 25 07:23 ./runcmd So as far as I can tell, the command terminated successfully and left the 'exit.tmp' with the content of '0'. Furthermore, moving the file `shared/exit.tmp` -> `./shared/job.kdzgmbyv/exit` allowed autopkgtest to proceed with the tests and pass them successfully. I am still wondering why this appears to happen only in some conditions. Is it the amount of output caused by the large number of build-depends? -- not sure. -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.11.9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set 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.9.11 ii libdpkg-perl 1.22.11 ii mawk 1.3.4.20240905-1 ii procps 2:4.0.4-6 ii python3 3.12.6-1 ii python3-debian 0.1.49 ii python3-distro-info 1.12 ii retry 1.0.5-3 Versions of packages autopkgtest recommends: ii autodep8 0.28+nmu1 ii fakeroot 1.36-1 Versions of packages autopkgtest suggests: ii docker-cli 26.1.5+dfsg1-4 ii docker.io 26.1.5+dfsg1-4 ii fakemachine 0.0.10-1+b3 ii genisoimage 9:1.1.11-3.5 pn incus <none> ii lxc 1:6.0.2-1 pn lxd <none> ii ovmf 2024.08-4 pn ovmf-ia32 <none> ii podman 5.2.5-1 ii qemu-efi-aarch64 2024.08-4 ii qemu-efi-arm 2024.08-4 pn qemu-efi-riscv64 <none> ii qemu-system 1:9.1.1+ds-5 ii qemu-utils 1:9.1.1+ds-5 ii schroot 1.6.13-5 ii util-linux 2.40.2-11 ii vmdb2 0.40-2 ii zerofree 1.1.1-1+b1 -- no debconf information
