Source: apparmor Version: 2.13.3-7 X-Debbugs-CC: debian-ci@lists.debian.org Control: affects -1 autopkgtest Control: affects -1 debci Dear maintainer(s), I'm not sure what's going on, but I wanted to at least inform you that the apparmor autopkgtest is not working smoothly on the ci.debian.net infrastructure. Something in the test is very often preventing autopkgtest (the binary) from stopping and cleaning up the lxc container within the 600 seconds it gets to do that, which leads to a tmpfail for the apparmor autopkgtest and a still running lxc container on the worker. Obviously there's a bug somewhere in either lxc and/or autopkgtest, as you shouldn't be able to break the infrastructure in this way, but maybe you have a clue what could be the cause of this and help us to fix the underlying issue. Your autopkgtest itself normally passes before causing the issue. One thing that may be required in your test if the test itself doesn't get updated is to mark it as isolation-machine although I'd like to understand the issue a bit better to know for sure. We can see this issue happening at least as far back as 2019-12-05 09:19:03 UTC on amd64 unstable, I haven't checked all the logs. Paul
Attachment:
signature.asc
Description: OpenPGP digital signature