On Mon, Jul 18, 2022 at 09:07:28PM +0200, Paul Gevers wrote: > Source: liburing > Version: 2.1-2 > Severity: important > X-Debbugs-Cc: br...@ubuntu.com > > Dear Guillem, > > 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.
I managed to capture some information from an instance in an Ubuntu bug report - http://launchpad.net/bugs/1981636. -- Brian Murray @ubuntu.com
