Tests fail on Github's CI Ubuntu 24.04 workers

[notatallshaw]

See #13152 and #13556.

When switching from ubuntu-22.04 to ubuntu-24.04 or ubuntu-latest GitHub CI workers, the following tests fail:

FAILED tests/functional/test_pep668.py::test_fails[install] - AssertionError: Script passed unexpectedly:
Script result: python -m pip install pip
FAILED tests/functional/test_pep668.py::test_fails[install-user] - AssertionError: Script passed unexpectedly:
Script result: python -m pip install --user pip
FAILED tests/functional/test_pep668.py::test_fails[install-dry-run] - AssertionError: Script passed unexpectedly:
Script result: python -m pip install --dry-run pip
FAILED tests/functional/test_pep668.py::test_fails[uninstall] - AssertionError: Script passed unexpectedly:
Script result: python -m pip uninstall -y pip
FAILED tests/functional/test_vcs_bazaar.py::test_ensure_bzr_available - subprocess.CalledProcessError: Command '('bzr', 'version', '--short')' returned non-zero exit status 1.

I cannot reproduce locally (on Ubuntu 24.04) and I've not had time to do further debugging and the errors are well outside by wheel house.

So if someone else wants to take a look, I will be willing to review solving some but not all of them (perhaps enable the CI for ubuntu-latest as a separate job and then remove latest before merging).

Otherwise I will eventually go back to debugging them,

[notatallshaw]

I am going to assign this issue to GitHub Copilot and "see what happens", my hope is that GitHub Copilot finds a simple configuration issue and doesn't start making a big mess of the test suite to try and fix this. I do not plan to "guide" GitHub Copilot, if it fails to find a working test configuration for ubuntu-24.04 or ubuntu-latest I will close the PR.

If GitHub Copilot does find a simple solution I plan to try and reproduce locally and raise a PR independently.

If any other maintainer objects I am happy to close the GitHub Copilot raised PR.

[notatallshaw]

I am going to assign this issue to GitHub Copilot and "see what happens"

"see what happens" turned out to be GitHub Copilot failing to find any solution after multiple attempts. In retrospect I realize that my assumption was that GitHub Copilot would be able to iterate in the GitHub CI environment, but it seemingly doesn't have access to the CI environment itself, and wasn't unable to iterate based on CI failures (it required repeated prompting that CI had failed).

This did make me think two things:

• I should try reproducing on a clean Ubuntu install with the Ubuntu provided Python and venv (currently I've been using my own or third party builds)
• The Ubuntu distro run test suites for the packages they bundle, perhaps they have patched pip or it's tests to work on Ubuntu 24.04+, maybe I can find those patches

I don't know when I'll have time for this, so if someone else wants to pursue this they are more than welcome.