Since Fedora Rawhide moved to Python 3.11 and cleared up container images, there are few issues that need to be solved before Azure Ci will be working again with fedora:rawhide container image. Below is the list if issues in no particular order:
fedora:rawhide
su
sudo
fedora-toolbox:39
pypi
pypi: 674 E failed with /__w/1/s/.tox-install.sh (resolves to /__w/1/s/.tox-install.sh) is not allowed, use allowlist_externals to allow it [tox/session/cmd/run/single.py:55] pypi: FAIL ✖ in 0.18 seconds
libgbm.so.1
... `-- puppeteer-core@19.7.2 ... Fatal error: Failed to launch the browser process! /home/vsts_azpcontainer/.cache/puppeteer/chrome/linux-1095492/chrome-linux/chrome: error while loading shared libraries: libgbm.so.1: cannot open shared object file: No such file or directory
About tox failure. Fedora 38+ ships tox 4.x that no longer allows 'external' executables.
allowlist_externals must be used: https://tox.wiki/en/latest/config.html#allowlist_externals
allowlist_externals
About chromium deps issue. - chromium's deps can be pulled with the installation of corresponding rpm package - distro chromium can be used instead of Puppeteer's one https://github.com/gruntjs/grunt-contrib-qunit#qunit-task
When installed by npm, this plugin will automatically download and install a local Chrome binary within the node_modules directory of the Puppeteer library, which is used for launching a Chrome process. If your system already provides an installation of Chrome, you can configure this plugin to use the globally installed executable by specifying a custom executablePath in the puppeteer launch options. This will almost certainly be needed in order to run Chrome in a CI environment
Metadata Update from @ftrivino: - Custom field on_review adjusted to https://github.com/freeipa/freeipa/pull/6744
master:
ipa-4-10:
ipa-4-9:
Metadata Update from @abbra: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.