Hi, intrigeri (2021-02-06): > I understand the LXC container is stopped and restarted between each > test, so what Paul wrote above suggests the container is successfully > stopped between the 1st and 2nd test, same between the 2nd and 3rd > test, but then it occasionally fails to stop after the last > (3rd) test. Correct? > > If this analysis is correct, then the culprit has to be in the 3rd > test i.e.: > > # Dummy test so that changes to linux-image-amd64 trigger our other > autopkgtests > # on ci.debian.net > Test-Command: /bin/true > Depends: linux-image-amd64 [amd64] | linux-image-generic [ amd64 ] > Restrictions: superficial, skip-not-installable > > … and this is the one I should mark it as isolation-machine, > so we can resume running the other 2 tests on ci.d.n, > which I would very much like. > > Makes sense?
Actually, apparmor-profiles-extra has the exact same test, and AFAICT it seems to run pretty reliably there, so I now have doubts about the hypothesis I quoted above. Still, perhaps it's worth trying to add isolation-machine to that test, remove src:apparmor from the blocklist, and see what happens? Cheers!