Repository navigation
Cygwin job is broken on "Set up virtualenv" step #2004
Description
Activity
It is very puzzling indeed, and seemingly impossible to error out without any form of message.
- added a commit that references this issue
on Feb 21, 2025 The absence of output is due to
venvnot showing the error in its output. In 4605dd6, I hadvenvnot installpipbut instead attempted to do so in a very similar way to howvenvdoes, in a subsequent step. That produces this error:Traceback (most recent call last): File "/usr/lib/python3.9/runpy.py", line 188, in _run_module_as_main mod_name, mod_spec, code = _get_module_details(mod_name, _Error) File "/usr/lib/python3.9/runpy.py", line 147, in _get_module_details return _get_module_details(pkg_main_name, error) File "/usr/lib/python3.9/runpy.py", line 111, in _get_module_details __import__(pkg_name) File "/usr/lib/python3.9/ensurepip/__init__.py", line [30](https://github.com/EliahKagan/GitPython/actions/runs/13454947366/job/37596811693#step:10:31), in <module> _SETUPTOOLS_VERSION = _get_most_recent_wheel_version("setuptools") File "/usr/lib/python3.9/ensurepip/__init__.py", line 27, in _get_most_recent_wheel_version return str(max(_wheels[pkg], key=distutils.version.LooseVersion)) ValueError: max() arg is an empty sequenceI haven't found a good way to fix this entirely, but in #2007 I have worked around it by having the Cygwin CI job install
pipin the virtual environment using the bootstrap script, which fixes the problem that kept tests from running, but does not fix the problem fortest_installationwhere it also separately occurs.- added a commit that references this issue
on Feb 25, 2025 #2053 fixes this properly (at least with Python 3.9, which is all we test on Cygwin currently).
The Cygwin CI test job is failing now, including when rerun at the tip of the main branch where it formerly passed. The failure occurs in the "Set up virtualenv" step, which runs
python -m venv .venv. The log does not how a detailed error message, just:I first noticed this when checking the current status of #1988 (see #1988 (comment)), but it is not specific to that PR.
I do not know why this happens.