Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-20 Thread Paul Gevers
Hi, On 20-02-2022 11:04, Shengjing Zhu wrote: That's great to know. Could you retry runc's autopkgtest on ci-worker13. If it succeeds, can we close this bug? I hit the retry button three times, two of those were executed on ci-worker13 and all three passed. Paul OpenPGP_signature Descript

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-20 Thread Shengjing Zhu
On Sun, Feb 20, 2022 at 6:00 PM Paul Gevers wrote: > > Hi, > > On 20-02-2022 09:20, Shengjing Zhu wrote: > > 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 tha

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-20 Thread Paul Gevers
Hi, On 20-02-2022 09:20, Shengjing Zhu wrote: 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. That wasn't possible until a cou

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-20 Thread Shengjing Zhu
On Thu, Feb 17, 2022 at 4:39 AM Paul Gevers 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

Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers

2022-02-16 Thread Paul Gevers
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 autopk