Source: liburing
Version: 2.1-2
Severity: important
X-Debbugs-Cc: brian@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.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 486 |
Nodes: | 16 (2 / 14) |
Uptime: | 138:56:34 |
Calls: | 9,657 |
Calls today: | 5 |
Files: | 13,708 |
Messages: | 6,167,231 |