Bug#1106397: debvm: flaky autopkgtest: exp3 not open

2025-05-29 Thread Helmut Grohne
Control: clone -1 -2 Control: reassign -2 qemu-system-x86 Control: retitle -2 qemu-system-x86_64: system/physmem.c:2680: iotlb_to_section: Assertion `section_index < d->map.sections_nb' failed. Control: severity -2 important Control: block -1 by -2 Control: affects -1 + debvm On Wed, May 28, 2025

Bug#1106397: debvm: flaky autopkgtest: exp3 not open

2025-05-28 Thread Paul Gevers
Hi, On 28-05-2025 10:56, Helmut Grohne wrote: I uploaded 0.4.2 limiting concurrency to 4 CPUs at most. Thanks. Only later I realized that while amd64 has 64 cores, e.g. ppc64el and s390x also have quite some cores available (16 resp. 10), but there we haven't seen the fallout. I schedule

Bug#1106397: debvm: flaky autopkgtest: exp3 not open

2025-05-28 Thread Helmut Grohne
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

Bug#1106397: debvm: flaky autopkgtest: exp3 not open

2025-05-25 Thread Helmut Grohne
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 >

Bug#1106397: debvm: flaky autopkgtest: exp3 not open

2025-05-24 Thread Paul Gevers
Source: debvm Version: 0.4.1 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), 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 l