chore(deps): update dependency libcgroup/libcgroup to v3

[nicholasdille-bot]

This PR contains the following updates:

Package	Update	Change
libcgroup/libcgroup	major	2.0.3 -> 3.0

---

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.

---

Release Notes

libcgroup/libcgroup (libcgroup/libcgroup)

v3.0

Compare Source

NOTE - this release is not guaranteed to be backward compatible with previous releases

ChangeLog

• Version 3.0 - August 5, 2022
  • Introduce cgxget and cgxset - tools to abstract cgroup v1 and v2 systems
  • Introduce new C APIs that abstract the cgroup v1 and v2 interfaces for the user
  • Remove the cgclear tool
  • Introduce modern Cython-based Python bindings, replacing the old bindings
  • Add spdx license tags across the files
  • Introduce a process for handling security-related vulnerabilities
  • Fix many warnings and errors reported by coverity
  • Add full cgroup v2 support to continuous integration
  • Add code quality analysis to continuous integration
  • Add Linux kernel syntax style and add checking to continuous integration

Checksum

Hash: SHA256

8d284d896fca1c981b55850e92acd3ad9648a69227c028dda7ae3402af878edd  libcgroup-3.0.0.tar.gz
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEER6aPzjfH1wJP1l4RNWzmLCtSQJkFAmLsOzsACgkQNWzmLCtS
QJkENhAAzWVgGYIcVtT66zby4Tc1o5RWoEzJBGnKsoobo45oA7if65wUKYfxhMZz
/VZNT2nZ6QlnwtFXMMRgBFxmbHB/Y+/5k9zQSOS+vLSfYkN/kCY+uJHpTYuXiH0H
KlCwPvoUU/deAub0M08cKvPMkvPXKBChYDJvQcxpNLt1wig6Mxgey120NrfTrTCe
hOHh7gNqTRS/qA8VH8bvhfrmRgCdAmAIC6NYhS9RvNwUnkNKpTwFAClGOCv70wHf
tF+jTcRZ+xvHw1r6GL7cngsj7LQiZZ2RWsNGJ0Ynr1UfpwX+8qMtBYpV0YOAEei5
BYepi5vVnc/wC1KMQFRJgpl6hR1pQiz+nlwvUuJW9nge6zWedcKiX0QUWIHixWXw
JfMFNR/A8hX8L1AhNpzUbrYsCeIIo7K55qgNWR7QOaJVp6CJVU0Vu3Ww350AOOHN
nWOPvrzRu8DpwXIJK02o7cU/NbCANDHgFvCTkmXxskDDiOTVw+RcFeWtQfwptbyj
u55ZQTkvZxvE661abFX7gbnZTYp3Cla4UmIjjqBCJI2VLS5J/j5O8G0GwyGppyZt
G114iNB2DYebPhV9qOrekN5ICbWPKQXPT22DR0GA1TPWl6b10LqkEUxmqPR9kUEA
y7AREB3PAspXffPckboSIfmq5KNDUhLo17NfGr+L0qM3iPbOkPQ=
=gtT8
-----END PGP SIGNATURE-----

Note while building:

This release utilizes both unit and functional tests - googletest for unit testing and a small python framework for functional testing. The functional tests can be run in a container or on a bare-metal machine. By default, all unit and all functional tests are enabled. The bare metal tests will alter your cgroup hierarchy, and I strongly encourage running them on a temporary VM or other "disposable" machine. They should not be destructive, but cgroups are obviously a critical building block of a Linux system, and I would hate to see a critical machine harmed.

To completely disable the containerized functional tests:

• Comment out the ./ftests.py line in ftests.sh

To completely disable the bare-metal functional tests:

• Comment out the ./ftests.py line in ftests-nocontainer.sh

To disable a failing test (in either a container or on bare metal):

• Tests can be skipped by providing the --skip flag to ftests.py. Currently test number 28 is being skipped in ftests-nocontainer.sh
  To skip a single test, then use the format --skip 9
  To skip multiple tests, then use the format --skip 9,10,13

./configure && make should succeed on all distributions. If there is a failure with these steps, please email the libcgroup development team via our mailing list - [email protected] - or open a Github issue here - https://github.com/libcgroup/libcgroup/issues

make check may fail on some distributions and some machines. You are welcome to send any failures to our mailing list or open a Github issue, but note that some failures may be expected. The functional tests are currently focused on our continuous integration machines on Github Actions. Tests that enumerate all cgroup settings for a given controller may produce different results on other machines - especially if a different distro or kernel is being used. See below for details on potential failures:

• Functional tests fail - lxd: command not found - Some of the functional tests use LXD containers to safely encapsulate cgroup changes that would otherwise be destructive on a live system, but not all distributions currently support LXD. If so, feel free to bypass running the LXD functional tests. See the comment above on how to disable the containerized tests

• Various functional tests fail - As outlined above, this is likely due to differences in system capabilities. For example, if your system has real time cgroups enabled, then you will likely see functional test number 9 fail. I would recommend adding it to the skip list in ftests.sh and/or ftests-nocontainer.sh. See the comment above on how to skip individual tests

• Unit tests fail - version GLIBCXX_3.4.20 not found - version CXXABI_1.3.9 not found - version GLIBCXX_3.4.21 not found To facilitate long-term stability and testability, we have bundled a compiled version of googletest with this release of libcgroup. On older distributions, this could cause errors during make check` due to the googletest *.so files being dependent upon a newer version of glibc than is available. This can be easily remedied by re-compiling googletest and replacing the provided *.so files. The rough steps are outlined below:

  $ git clone https://github.com/google/googletest.git googletest
  $ cd googletest
  $ git checkout release-1.8.0
  $ cd googletest
  $ cmake -DBUILD_SHARED_LIBS=ON .
  $ make
  $ cp *.so {path_where_you_extracted_libcgroup}/googletest/googletest
  $ cd {path_where_you_extracted_libcgroup}/tests/gunit
  $ make clean
  $ make check

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[nicholasdille-bot]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.