Nothing complicated, just a very simple 'run' command.
Currently fails, which is good, it means this test
would have caught today's crisis[1]. Unfortunately
it fails with no useful info whatsoever: the test
result simply shows ERROR. I'm not sure there's much
I can do about this, since podman itself is silent
on the failure. (It'd be nice if gating tests at least
showed us the exit status).
[1] https://github.com/containers/container-selinux/issues/169
Signed-off-by: Ed Santiago <santiago@redhat.com>
Add very basic smoke tests that check if the container module installed
successfully and that it is still possible to rebuild the policy after
installing the package.
This, along with enabling rawhide gating [1], should help catch issues
like [2] and prevent a broken build from getting into Rawhide composes.
[1] https://docs.fedoraproject.org/en-US/rawhide-gating/
[2] https://github.com/containers/container-selinux/pull/84
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
