On Friday, August 21, 2026 3:00:40 PM Mountain Standard Time Soren Stoutner wrote: > On Friday, August 21, 2026 8:59:15 AM Mountain Standard Time Paul Gevers > > wrote: > > Don't hesitate to reach out if you need help and some more information > > from our infrastructure. > > I have never been able to replicate these autopkgtest failures locally (sbuild > unshare chroot), but I have seen them on debci and Salsa CI. Is there > anything about the debci autopkgtest environment (possibly a resource > restriction) that might cause them to fail?
A piece of additional information that may be helpful: the tests used to be run in parallel. When doing so, I would see inconsistent failures on Salsa CI. With this release I switched the tests to be run sequentially, and the Salsa CI failures disappeared. This would usually lead me to believe that it might be a problem with either CPU constraints (causing the tests to timeout when run in parallel) or RAM constraints (causing a tests to fail if the RAM is exhaused). I do not see any OOM errors in the logs. When running the tests locally, no part of the entire build-test process consumes more than 6GB of RAM. During build CPU usage can consume a single core entirely, but during the autopkgtests CPU usage doesn’t rise above 25% of a single core. So, I have a hard time imagining either of those being the problem. -- Soren Stoutner [email protected]
signature.asc
Description: This is a digitally signed message part.
