Hi! On Mon, 2022-07-18 at 21:07:28 +0200, Paul Gevers wrote: > Source: liburing > Version: 2.1-2 > Severity: important > X-Debbugs-Cc: br...@ubuntu.com
> Some days ago (approximately 7) the autopkgtest of liburing started to > behave badly on the Debian and Ubuntu infrastructure. It's not totally > clear to me what happens, but I have lxc containers left behind after > the test that I can't clean up. > > A similar thing seems to happen on the Ubuntu side because they have > blocked the test from running recently and I'll do the same on our > side. > > https://git.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-package-configs/commit/?id=fedf747ea808837217d373773d105f242819702d > > Because your package didn't change in that time, I suspect one of your > dependencies caused liburing to behave differently. It would be great > if we figured out what that is. While only having skimmed over the logs, the first suspect for me would be the Linux kernel, where liburing might be triggering some kernel bug. Were the systems upgraded around that time with a newer kernel version (is that a 5.18.x from bpo)? The only other options if that would not have been the case that seem plausible would be glibc (which was uploaded on the 10th, and could be a suspect), or lxc itself or similar, but that has not been uploaded for a while in sid. Thanks, Guillem
