[Pkg-libvirt-maintainers] Bug#1004562: libguestfs: autopkgtest regression

[Paul Gevers]

Hi,

On Sun, 30 Jan 2022 17:07:53 +0200 Adrian Bunk <bunk at debian.org> wrote:
> https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libguestfs/18786402/log.gz
> 
> ...
> + ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa -T -p 10022 -o ConnectTimeout=5 root at localhost echo success
> Connection timed out during banner exchange
> Connection to 127.0.0.1 port 10022 timed out
> + rv=1
> + [ 1 -eq 0 ]
> + sleepenh 1643405863.414064 5
> + [ 1 -eq 1 ]
> + TIMESTAMP=1643405868.414064
> + i=39
> + [ 39 -ge 40 ]
> + true
> + rv=0
> + ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa -T -p 10022 -o ConnectTimeout=5 root at localhost echo success
> Connection timed out during banner exchange
> Connection to 127.0.0.1 port 10022 timed out
> + rv=1
> + [ 1 -eq 0 ]
> + sleepenh 1643405868.414064 5
> + [ 1 -eq 1 ]
> + TIMESTAMP=1643405873.414064
> + i=40
> + [ 40 -ge 40 ]
> + break
> + [ 40 -eq 40 ]
> + echo timeout reached: unable to connect to qemu via ssh
> + exit 1
> + cat --show-nonprinting qemu.log
> + kill 26114
> autopkgtest [21:37:54]: @@@@@@@@@@@@@@@@@@@@ summary
> extlinux             FAIL non-zero exit status 1

On top of this, your test depends on linux-image-amd64 which is only 
available on amd64. Hence, the test fails on all other architectures.

So, apart from an "Architecture" field in d/t/control, I'm pretty sure 
you also need a "isolation-machine" restriction, because depending on a 
linux image package is futile in other environments. You're starting 
qemu inside your test. That doesn't go well in lxc.

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-libvirt-maintainers/attachments/20220201/8f4e8510/attachment.sig>