Test Pipeline

[daberkow]

Hi!

Sorry that I removed the template, but I dont think it fit this issue exactly. The repo seems to be having issues with the new matrix test pipeline. I think it comes down to SELinux is a low-level security system and running it in Docker containers in Actions seems to cause issues.

First the containers seemed to fail with SELinux not installed, and the default checks to install it failing. Then I got it installed in a branch (https://github.com/daberkow/puppet-selinux/actions/runs/9377228889/job/25818459030) but because we are in containers they dont restart and fully init SELinux. I was curious if you have seen this. I can continue to play with it and see if I can get it to work, but we may need to pivot to get things happy. I am more familiar with CircleCI, and there you can spawn "Machine" vms which alow you to work more low level. Perhaps Actions has a similar thing where we can get more of a VM than a container?

My main point is: I am trying to get #382 over the hill and into the repo. Are we ok if we move the CI pipeline around and change the default from the system most of the repos in this org use if that is the only way to make SELinux tests work?

Dan

[kenyon]

This is a known problem with several of our modules that can't be tested in Docker containers. #383 is an attempt to have the acceptance tests run in virtual machines.