]> git.ipfire.org Git - thirdparty/libcgroup.git/commit
github: dist: Rework the automated functional tests
authorTom Hromatka <tom.hromatka@oracle.com>
Tue, 8 Apr 2025 22:42:23 +0000 (16:42 -0600)
committerKamalesh Babulal <kamalesh.babulal@oracle.com>
Thu, 10 Apr 2025 09:38:30 +0000 (15:08 +0530)
commit8785d6e68bbb2e395ba51a97af79908d9a23b9e9
treeddcb7fafcd5c923f89d92658cbf6632dceb988dc
parentf90323db11e10b2d81f7b9aa77d045d0acaf6526
github: dist: Rework the automated functional tests

Now that Github Actions don't support cgroup v1, we can make the github
runners run the tests in a more granular fashion.  Add a runner to
individually run the containerized tests, the non-containerized tests,
and the sudo tests.  This simplifies the testing logic, and should help
us better identify failures.

As part of this, no longer run ftests-wrapper.sh when `make check` is
invoked on the ftests directory.  This is an undue burden for distros
as it requires uncommon dependencies (lxc, etc.) and can adversely
affect the cgroup sysfs filesystem on the build system.  The onus is
on upstream libcgroup to provide a well-tested and vetted *.tar.gz for
the distros that they can then just package up and disseminate.  They
shouldn't have to deal with challenging tests and test configurations.

Signed-off-by: Tom Hromatka <tom.hromatka@oracle.com>
Signed-off-by: Kamalesh Babulal <kamalesh.babulal@oracle.com>
.github/workflows/continuous-integration.yml
tests/ftests/084-sudo-cgcreate_systemd_scope_pid.py
tests/ftests/Makefile.am
tests/ftests/ftests-container.sh [new file with mode: 0755]
tests/ftests/ftests-nocontainer.sh [new file with mode: 0755]
tests/ftests/ftests-sudo.sh [moved from tests/ftests/ftests-wrapper.sh with 53% similarity]