-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Builds for Helix Dockerfiles are all failing setting up virtual environment #1090
Comments
[Triage] @garath Helix python setup is failing in Helix Docker images. Is this related to yesterday's Helix rollout? |
Possibly... I'm not sure how to debug this. Do you have any pointers? What is this pipeline doing? |
It's just building Dockerfiles. You can repro by building this Dockerfile, for example. |
So you suspect there was a change dnceng made that was deployed in the last rollout that broke this? (Sorry for being pedantic, I'm not seeing anything familiar or anything obviously connecting it to the rollout so I'm trying to find some touchpoints.) |
Nobody on our team is very knowledgeable on Python so we're just guessing here. But this is what might be the cause:
So if something recently rolled out there it could impact the behavior in the build here. |
It also might be purely in the realm of a Python change, unrelated to Helix. We're not sure yet. |
Looking at the change history... I see no changes related to either the helix client or the version of Python we install on machines. Hmm... |
... or Helix |
Related: #1093 |
When helix images are launched, what does that look like? Does anyone have a link to the script that does that? That would be super useful. |
This command is failing:
RUN python3 -m virtualenv /home/helixbot/.vsts-env
Example build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=705519&view=results
The text was updated successfully, but these errors were encountered: