Bug#1059725: autopkgtest: isolation-machine test fails: nearly all tests in podman-init fail

[Paul Gevers]

Hi,

Currently the autopkgtest of autopkgtest is in a very sad state on amd64
on ci.d.n because of podman-init. The test times out after:

5171s Preparing to unpack .../libc6_2.37-14_amd64.deb ...
5171s Unpacking libc6:amd64 (2.37-14) over (2.37-13) ...
5171s Setting up libc6:amd64 (2.37-14) ...

with

15146s autopkgtest [04:14:17]: ERROR: timed out on command "su -s
/bin/bash debci -c set -e; exec /tmp/autopkgtest.fAxx5b/wrapper.sh
--artifacts=/tmp/autopkgtest.fAxx5b/podman-init-artifacts
--chdir=/tmp/autopkgtest.fAxx5b/build.ae2/src
--env=DEB_BUILD_OPTIONS=parallel=1 --env=DEBIAN_FRONTEND=noninteractive
--env=LANG=C.UTF-8 --unset-env=LANGUAGE --unset-env=LC_ADDRESS
--unset-env=LC_ALL --unset-env=LC_COLLATE --unset-env=LC_CTYPE
--unset-env=LC_IDENTIFICATION --unset-env=LC_MEASUREMENT
--unset-env=LC_MESSAGES --unset-env=LC_MONETARY --unset-env=LC_NAME
--unset-env=LC_NUMERIC --unset-env=LC_PAPER --unset-env=LC_TELEPHONE
--unset-env=LC_TIME --script-pid-file=/tmp/autopkgtest_script_pid
--source-profile --stderr=/tmp/autopkgtest.fAxx5b/podman-init-stderr
--stdout=/tmp/autopkgtest.fAxx5b/podman-init-stdout
--tmp=/tmp/autopkgtest.fAxx5b/autopkgtest_tmp
--make-executable=/tmp/autopkgtest.fAxx5b/build.ae2/src/debian/tests/podman-init
-- /tmp/autopkgtest.fAxx5b/build.ae2/src/debian/tests/podman-init"
(kind: test)
15146s autopkgtest [04:14:17]: test podman-init: -----------------------]
15446s qemu-system-x86_64: terminating on signal 15 from pid 2725202
(/usr/bin/python3)

Following that it fails to run the next test:

15447s autopkgtest: WARNING: Copying up test output timed out, ignoring
15447s autopkgtest [04:19:18]: test podman-init: - - - - - - - - - -
results - - - - - - - - - -
15447s podman-init FLAKY timed out
15447s autopkgtest [04:19:18]: test schroot: preparing testbed
15447s autopkgtest [04:19:18]: ERROR: testbed failure: cannot send to
testbed: 'NoneType' object has no attribute 'stdin'

Which cause the test to fail with an tmpfail exit code. I'm seriously
wondering if the failure to setup the testbed for the next test is
actually a generic autopkgtest problem (maybe of the qemu backend). What
do people think?

I'm going to disable the podman-init test completely until somebody
looks into this and for the short term I've put autopkgtest on the
reject_list of ci.d.n for amd64.

Paul