gets stuck in ansitowin32.py on GitLab CI #3534
Comments
|
Could you please show your gitlab CI's configuration to help debugging? |
|
Yes, of course. I'm sorry: ---
variables:
# removing this doesn't change anything:
PIPENV_VENV_IN_PROJECT: 1
stages:
- setup
- lint
- check_dependencies
- test
setup:
stage: setup
script:
# here it fails. It's the very first command, that will be executed:
- pipenv install
- ./setup-devel.sh
tags:
- docker
# the following is for completeness but should not be related to the issue
django_check:
stage: lint
script:
- pipenv run manage.py check --fail-level=INFO
tags:
- docker
translation_check:
stage: lint
script:
- pipenv run translation_check
tags:
- docker
prospector:
stage: lint
script:
- prospector --zero-exit
tags:
- docker
npm_check_update:
stage: check_dependencies
script:
- yarn global add npm-check-updates
- ncu --error-level 2
allow_failure: true
tags:
- docker
pipenv_check:
stage: check_dependencies
script:
- PYTHON_VERSION=$(python3 -c 'import sys; print(f"{sys.version_info.major}.{sys.version_info.minor}")')
- sed -i "s/python_version =.*/python_version = \"${PYTHON_VERSION}\"/" Pipfile
- pipenv check
tags:
- docker
test:
stage: test
script:
- pipenv run test
coverage: /^TOTAL\s+\d+\s+\d+\s+(\d+\%)$/
tags:
- docker
...But as I said, I could not reproduce it on gitlab.com... I've also corrected the |
|
I could finally reproduce it 🎉 Inside a project, that uses pipenv, run: docker run --rm -it -v `pwd`:/srv/:Z fedora bash
# install pipenv and tox
dnf -y install pipenv python3-tox procps-ng
cd /srv/
# ensure that virtual env does not yet exist
rm -rf .venv
export PIPENV_VENV_IN_PROJECT=1
# set the env var CI
export CI=true
# run pipenv without a TTY
setsid sh -c 'tty; ps -jp "$$"; env; pipenv install' < /dev/null > log 2>&1
# see that pipenv is still running
ps aux
# ...but there is no output (if LANG was not set, you can read that pipenv is complaining about)
tail -f logNow the CPU runs at 100% on one core and pipenv stucks. It looks like a combination of:
I hope, you are able to reproduce it now and find the problem... |
|
This may be a bug (I think I've run into this before when combining FYI Alternative approaches include forcibly setting |
techalchemy
added
Status: Awaiting Update ⏳
Thanks for that. In fact it works, when you add a shebang to Unfortunately it does not work with any of the variables exported:
The colors are of course disabled, when running pipenv with a TTY. But the bug as described above still exists. As workaround I'll add an diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 5205b24..b3c08ff 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -2,6 +2,8 @@
variables:
PIPENV_VENV_IN_PROJECT: 1
+ # See https://github.com/pypa/pipenv/issues/3534:
+ CI: ""
stages:
- setup |
This worked like a charm, thanks @sedrubal I think we should bug an issue to Gitlab |
|
Crosslinking: #3575 |
|
Hrm, that's actually helpful though. Up and down the stack The error logs were even more helpful, I think this was a bug with the old stream wrapper we used to wrap the Using the following dockerfile I managed to reproduce the problem, which I then resolved simply by installing a wheel built from the master branch of pipenv -- I simply uncommented the specified line: FROM fedora as test-container
WORKDIR /srv/
RUN set -ex && dnf -y install pipenv python3-tox procps-ng
COPY Pipfile .
COPY pipenv-2018.11.27.dev0-py3-none-any.whl .
# Uncomment this line and things work
# RUN set -ex && python3 -m pip install --upgrade pipenv-2018.11.27.dev0-py3-none-any.whl tox
ENV CI true
ENV PIPENV_VENV_IN_PROJECT 1
# Install python requirements
RUN set -ex && setsid sh -c 'tty; ps -jp "$$"; env; pipenv install' < /dev/null > log 2>&1
RUN set -ex && ps -aux
RUN set -ex && tail logMy pipfile for this build contains: [[source]]
url = "https://pypi.org/simple"
verify_ssl = true
name = "pypi"
[packages]
django = "<=2.2.0"
[dev-packages]
[requires]
python_version = "3.6"With the |
Issue description
When running
pipenv installorpipenv syncon GitLab CI, pipenv gets stuck (at least for 1h, until the job gets killed).Expected result
It should not get stuck.
Actual result
--verbosedoes not print any more information. WhenLANGis set properly, you can't see any output, otherwise you can readand after that it hangs.
Steps to replicate
Unfortunately I couldn't reproduce it on gitlab.com. It happens on our private gitlab in a private repo. Here is a minimal version of a Pipfile:
I only run
pipenv installorpipenv sync.While the job was running / stuck in GitLab CI, I run the exact same command within the docker container, where the CI job was running and it worked. I think, the problem has something to do with how GitLab CI runs the commands. I thought, the problem might be, that
stdoutis not a tty, but running something likesetsid sh -c 'pipenv install' < /dev/null > log 2>&1did work, too.I tried running
python3 -m trace --trace /usr/bin/pipenv install > trace_log.txtand this is the outputtrace_log.txt
I removed many lines. I think, the last ones are interesting. At the end, it seems, that pipenv is looping forever over:
I already spent hours on debugging, but now, I don't know what to do...
$ pipenv --support
Pipenv version:
'2018.11.26'Pipenv location:
'/usr/lib/python3.7/site-packages/pipenv'Python location:
'/usr/bin/python3'Python installations found:
3.7.2:/usr/bin/python33.7.2:/usr/bin/python3.7m3.6.8:/usr/bin/python3.6m3.6.8:/usr/bin/python3.63.5.6:/usr/bin/python3.53.5.6:/usr/bin/python3.5m3.5.3:/usr/bin/pypy3.53.4.9:/usr/bin/python3.43.4.9:/usr/bin/python3.4m2.7.15:/usr/bin/python2.7.13:/usr/bin/pypyPEP 508 Information:
System environment variables:
CI_COMMIT_SHORT_SHAPIPENV_VENV_IN_PROJECTCI_RUNNER_EXECUTABLE_ARCHCI_COMMIT_TITLECI_JOB_TOKENCI_BUILD_REF_NAMECI_REGISTRY_PASSWORDCI_RUNNER_TAGSCI_PIPELINE_URLGITLAB_CI_PASSWORDCI_JOB_NAMECI_SERVER_VERSIONGITLAB_CICI_SERVER_REVISIONHOSTNAMECI_PROJECT_VISIBILITYCI_DISPOSABLE_ENVIRONMENTCI_COMMIT_SHACI_COMMIT_MESSAGECI_BUILD_STAGECI_PROJECT_URLCI_COMMIT_REF_SLUGCI_SERVER_NAMECI_RUNNER_VERSIONCI_BUILD_NAMECICI_REGISTRY_USERCI_PROJECT_IDCI_PIPELINE_IDCI_JOB_URLCI_COMMIT_DESCRIPTIONPWDGITLAB_FEATURESHOMECI_REGISTRYCI_BUILD_TOKENCI_BUILD_IDGITLAB_USER_NAMECI_COMMIT_BEFORE_SHACI_PROJECT_PATH_SLUGCI_API_V4_URLGITLAB_USER_EMAILCI_COMMIT_REF_NAMECI_SERVER_VERSION_PATCHCI_REGISTRY_IMAGECI_PIPELINE_IIDDISTTAGCI_SERVER_TLS_CA_FILECI_RUNNER_IDFGCCI_SERVERCI_JOB_IDCI_REPOSITORY_URLGITLAB_USER_LOGINCI_RUNNER_REVISIONCI_CONFIG_PATHCI_PROJECT_NAMECI_SERVER_VERSION_MINORCI_SERVER_VERSION_MAJORFF_K8S_USE_ENTRYPOINT_OVER_COMMANDCI_NODE_TOTALSHLVLCI_RUNNER_DESCRIPTIONNPM_TOKENCI_PROJECT_PATHGITLAB_USER_IDCI_BUILD_BEFORE_SHACI_BUILD_REFPATHCI_PIPELINE_SOURCECI_PROJECT_NAMESPACECI_PROJECT_DIRCI_JOB_STAGECI_BUILD_REF_SLUG_OLDPWDPIP_DISABLE_PIP_VERSION_CHECKPYTHONDONTWRITEBYTECODEPIP_SHIMS_BASE_MODULEPIP_PYTHON_PATHPYTHONFINDER_IGNORE_UNSUPPORTEDPipenv–specific environment variables:
PIPENV_VENV_IN_PROJECT:1Debug–specific environment variables:
PATH:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/binPWD:/The text was updated successfully, but these errors were encountered: