Hi Paul, On Sat, May 24, 2025 at 12:03:27PM +0200, Paul Gevers wrote: > I looked at the results of the autopkgtest of your package because it was > showing up in the excuses for dpkg. I noticed that it regularly fails on > amd64. Maybe you need to wait longer before deciding that starting the VM > failed?
I'm not sure extending the timout cuts it. For the record, the timeout presently is 5 minutes for start to login prompt. Shouldn't that work? > https://ci.debian.net/packages/d/debvm/testing/amd64/60842802/ The actual expect invocation started at 354s, so the time from expect invocation to test termination is 16 seconds < 300 seconds. > > 369s send: spawn id exp3 not open > 369s while executing > 369s "send "echo 6coF0JBW\$((2+3))\r"" > 369s (file "./tests/shell_interaction.expect" line 7) > 369s + cleanup > 369s + rm -f ssh_id ssh_id.pub test.img > 370s autopkgtest [04:17:32]: test debefivm-root: -----------------------] The error message hints at: https://sources.debian.org/src/expect/5.45.4-4/exp_command.c/?hl=209#L209 This suggests that qemu might have died. Also the location suggests that we did see a root shell prompt already. In another test, the error is different: https://ci.debian.net/packages/d/debvm/testing/amd64/60944789/#L9985 in debefivm-root 900s /usr/bin/debvm-waitssh: timeout reached trying to contact 127.0.0.1:2222 after waiting 540 seconds. One thing I notice here is that most amd64 tests run with 64 CPUs. debvm assigns the same amount of CPUs to the guest as the host has such that you can do compiling inside at full capacity. When using lots of CPUs and tcg emulation, this incurs quite a bit of slowness. How about limiting concurrency to at most four virtual CPUs? That should at least make the amd64 test noticeably faster. How do you see me validate a prospective change fixing the autopkgtest? The tests (and more) run in salsa-ci with few problems and locally, so the best I can do here is throwing changes at the archive and hoping that they fix. Would you agree to me doing an upload the limits concurrency and closes the flakiness bug with the idea that you'd reopen it if it doesn't fix? Helmut
