Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers
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 Description: OpenPGP digital signature
Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers
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 that by disabling > > relevant failed tests. > > That wasn't possible until a couple of days ago. Coincidentally I did > this yesterday. > That's great to know. Could you retry runc's autopkgtest on ci-worker13. If it succeeds, can we close this bug? -- Shengjing Zhu
Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers
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 couple of days ago. Coincidentally I did this yesterday. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers
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 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
Bug#1005891: runc: failing autopkgtest on one of ci.d.n amd64 workers
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. Don't hesitate to contact us at debian...@lists.debian.org if you need help debugging this issue. Paul https://ci.debian.net/data/autopkgtest/testing/amd64/r/runc/18799590/log.gz ok github.com/opencontainers/runc/libcontainer/utils 0.005s ? github.com/opencontainers/runc/types[no test files] FAIL dh_auto_test: error: cd _build && go test -vet=off -v -p 48 -tags seccomp github.com/opencontainers/runc github.com/opencontainers/runc/libcontainer github.com/opencontainers/runc/libcontainer/apparmor github.com/opencontainers/runc/libcontainer/capabilities github.com/opencontainers/runc/libcontainer/cgroups github.com/opencontainers/runc/libcontainer/cgroups/devices github.com/opencontainers/runc/libcontainer/cgroups/ebpf github.com/opencontainers/runc/libcontainer/cgroups/ebpf/devicefilter github.com/opencontainers/runc/libcontainer/cgroups/fs github.com/opencontainers/runc/libcontainer/cgroups/fs2 github.com/opencontainers/runc/libcontainer/cgroups/fscommon github.com/opencontainers/runc/libcontainer/cgroups/systemd github.com/opencontainers/runc/libcontainer/configs github.com/opencontainers/runc/libcontainer/configs/validate github.com/opencontainers/runc/libcontainer/devices github.com/opencontainers/runc/libcontainer/intelrdt github.com/opencontainers/runc/libcontainer/keys github.com/opencontainers/runc/libcontainer/logs github.com/opencontainers/runc/libcontainer/nsenter github.com/opencontainers/runc/libcontainer/nsenter/test github.com/opencontainers/runc/libcontainer/seccomp github.com/opencontainers/runc/libcontainer/seccomp/patchbpf github.com/opencontainers/runc/libcontainer/specconv github.com/opencontainers/runc/libcontainer/stacktrace github.com/opencontainers/runc/libcontainer/system github.com/opencontainers/runc/libcontainer/user github.com/opencontainers/runc/libcontainer/userns github.com/opencontainers/runc/libcontainer/utils github.com/opencontainers/runc/types returned exit code 1 make[1]: Leaving directory '/tmp/autopkgtest-lxc.v97d589s/downtmp/autopkgtest_tmp' make[1]: *** [debian/rules:24: override_dh_auto_test] Error 25 make: *** [debian/rules:11: build] Error 2 autopkgtest [13:11:41]: test dh-golang-autopkgtest: ---] OpenPGP_signature Description: OpenPGP digital signature
