Feature Request: run autopkgtest tests post-build
hlieberman opened this issue · comments
In the same vein as #9, it would be super awesome to run the autopkgtest suite after the build. (Probably using the autopkgtest-virt-null backend, since we're already inside an ephemeral container, so adding another layer of containerization is probably not worth it).
This is definitely on the roadmap and a thing I wanted to do for quite a while :-)
It hasn't been a high priority yet though (and I haven't looked into what is required to properly support autopkgtest - when it's added, we would highly likely want to integrate this with Laniakea and have the tests run regularly on e.g. PureOS packages via debspawn. But even without that, being able to run it locally for regular packaging would be very neat).
Because it's using
autopkgtest-virt-null, autopkgtest makes an assumption that the tests have
VM level isolation, rather than the container level isolation that they
actually do. This means some tests will either flake, fail, or potentially
cause undefined behavior that could affect the host.
That pretty much was the reason why I didn't touch this yet. But I think it may be possible to detect whether a certain test requires VM-level isolation and then skip it when run inside of the container (if that's not possible, I think such a feature would be useful in autopkgtest).