Hi Paul, On Sun, May 25, 2025 at 09:15:17PM +0200, Helmut Grohne wrote: > 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.
I uploaded 0.4.2 limiting concurrency to 4 CPUs at most. I scheduled 10 runs on amd64. https://ci.debian.net/user/helmutg/jobs Two of them failed in debefivm and not in debvm. It's still flaky, but maybe less so (or luck). Given the output, I'm quite sure that qemu actually hangs and that increasing any timeout does not buy us anything. To me, this feels like qemu and/or linux being randomly buggy. I note that I have never reproduced the specific failure mode outside ci.d.n. Any suggestions for how to move forward from here? Helmut
