[PATCH] tests: Handle system-wide tunables in rseq tests

[DJ Delorie]

Michael Jeanson <mjeanson@efficios.com> writes:
> I'm not sure what 'the container' is in this context but if it's a 
> generic way to isolate from the local system-wide tunables then yes it 
> would.

Yes, the test-container is a chroot we build at test time that has an
installed glibc and a few utilities (like sh and cp) and a basic
filesystem (like /etc).  It also has the build and source trees mounted
inside it.  "Running a test in a container" means running it with
support/test-container.c, which manages setting up the container
(refreshing the install and pre-installing any test-specific files
needed for the test), running the test in it, and cleaning up the
container afterwards.

The primary purpose of this system is to allow us to test things that
need to be tested "live" without interfering with (or being affected by)
the host OS.

See https://developers.redhat.com/blog/2018/11/16/microcontainers-for-unit-testing
for some introduction.