On Tue, 4 Jun 2024 at 05:57, Paul Gevers <elb...@debian.org> wrote: > I looked at the results of the autopkgtest of your package, because it > showed up in the glibc regressions. I noticed that it regularly fails on > amd64, ppc64el and s390x. For your info, as it seems to correlate, those > are the architectures where multiple tests run in parallel, each in > their own lxc container. > > Because the unstable-to-testing migration software now blocks on > regressions in testing, flaky tests, i.e. tests that flip between > passing and failing without changes to the list of installed packages, > are causing people unrelated to your package to spend time on these > tests. > > Don't hesitate to reach out if you need help and some more information > from our infrastructure. I'll need some help here, the lxc environment is doing something odd/wrong with the proc filesystem. We've been bit before from lxc, but I don't know enough about the CI system to know what's going on.
This *might* be fixed with a commit checking for odd ways LXC presents files[1] discussed at [2]. It also appears to be LXC version dependent. 1: https://gitlab.com/procps-ng/procps/-/commit/42dce4d9f4132360647c4dcae1fbbfa1171528b3 2: https://gitlab.com/libvirt/libvirt/-/issues/492 Ideally, I'd like to push a pre-release into the Debian CI and see if it works now. I'm not sure there is a way of doing that. - Craig
