Bug#1068363: src:autopkgtest: flaky autopkgtest (host dependent?) on ppc64el

2024-05-12 Thread Paul Gevers
Control: tags -1 pending Hi, On 06-04-2024 9:58 p.m., Paul Gevers wrote: Anyways, it looks like we could just lower the timeout to 1 second and hope were fine for some time to come. No. 1 second is *too short* for the PodmanRunner.test_copy_timeout test on salsa. So I'll just disable the

Bug#1068363: src:autopkgtest: flaky autopkgtest (host dependent?) on ppc64el

2024-04-06 Thread Paul Gevers
The mystery continues. On 04-04-2024 10:08 p.m., Paul Gevers wrote: I forgot that on amd64, autopkgtest's autopkgtest now runs in qemu which doesn't benefit yet as much from tmpfs as lxc does, so it's not a good comparison. On ci-worker13: """

Bug#1068363: src:autopkgtest: flaky autopkgtest (host dependent?) on ppc64el

2024-04-04 Thread Paul Gevers
Control: retitle -1 autopkgtest: test_copy_timeout fails on tmpfs Hi, On 04-04-2024 10:08 a.m., Paul Gevers wrote: Overall, I expect the host to be *faster* than the old hosts, but ironically the tests that seems to fail is: __main__.SchrootRunner.test_copy_timeout. Yes, it's too fast. The

Bug#1068363: src:autopkgtest: flaky autopkgtest (host dependent?) on ppc64el

2024-04-04 Thread Paul Gevers
Source: autopkgtest Version: 5.33 Severity: serious User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), I looked at the results of the autopkgtest of your package. I noticed that it recently started to fail a lot on ppc64el. The failures seem related to the host that runs the