On Thu, Feb 17, 2022 at 4:39 AM Paul Gevers <elb...@debian.org> wrote: > > Source: runc > Version: 1.1.0+ds1-1 > Severity: serious > X-Debbugs-CC: debian...@lists.debian.org > Tags: sid bookworm > User: debian...@lists.debian.org > Usertags: flaky > > Dear maintainer(s), > > I looked at the results of the autopkgtest of you package on amd64 > because with a recent upload of glibc the autopkgtest of runc > fails in testing. Recently (mid January) your packages started to fail > regularly and it seems to me that the failures are related to the > worker that the test runs on. ci-worker13 fails, while the other workers > are OK. Obviously I'm not sure it's related, but this particular host is > extremely powerful, 256 GB RAM and 48 cores.
It's because ci-worker13 still runs on the buster kernel. Any chance we can upgrade ci-worker13 to bullseye? So we can have a consistent testbed. Otherwise I can work around that by disabling relevant failed tests. -- Shengjing Zhu
