Closed
Description
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:
Run python -m venv .venv
python -m venv .venv
echo 'BASH_ENV=.venv/bin/activate' >>"$GITHUB_ENV"
shell: C:\tools\cygwin\bin\bash.exe --login --norc -eo pipefail -o igncr "{0}"
env:
CHERE_INVOKING: 1
CYGWIN_NOWINPATH: 1
CYGWIN:
+ python -m venv .venv
Error: Command '['/cygdrive/d/a/GitPython/GitPython/.venv/bin/python', '-Im', 'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1.
Error: Process completed with exit code 1.
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.
Activity
Byron commentedon Feb 21, 2025
It is very puzzling indeed, and seemingly impossible to error out without any form of message.
.git
subdir as anothersafe.directory
on Cygwin CI #1916Undo other chages besides using the bootstrap script
test_installation
#2007EliahKagan commentedon Feb 25, 2025
The absence of output is due to
venv
not showing the error in its output. In 4605dd6, I hadvenv
not installpip
but instead attempted to do so in a very similar way to howvenv
does, in a subsequent step. That produces this error:I 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
pip
in the virtual environment using the bootstrap script, which fixes the problem that kept tests from running, but does not fix the problem fortest_installation
where it also separately occurs.Merge pull request #2007 from EliahKagan/cygwin-py39-venv
Use python39-pip-wheel Cygwin package on CI
Use python39-pip-wheel Cygwin package on CI
Use python39-pip-wheel Cygwin package on CI
Mark `test_installation` xfail on Cygwin CI
test_installation
xfail on Cygwin CI #20098 remaining items