-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[Azure Pipelines] Consistently use the "Use Python Version" task #21722
Conversation
.azure-pipelines.yml
Outdated
@@ -229,9 +247,6 @@ jobs: | |||
- task: UsePythonVersion@0 | |||
inputs: | |||
versionSpec: '3.6.x' | |||
- task: UsePythonVersion@0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've asked about this in https://github.com/web-platform-tests/wpt/pull/20725/files#r377569491. It caused the job to start failing, so I'll probably revert and deal with it separately.
Waiting for CI to with all tests running before reverting and squashing into a single commit. |
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/use-python-version?view=azure-devops The default python/pip on the macOS VMs don't any longer. It may be possible to fix this, but to fix the urgent issue use the method that's supported by Azure Pipelines. The python version will remain unchanged at 2.7.17, but pip will change from 19.3.1 to 20.0.2. pip_install.yml can be simplified because the remaining code path is the same for macOS and Windows. Fixes #21691.
f4d3d00
to
76a93df
Compare
Don't what? (Work?). What I'm not understanding from this change is why we ever had anything that wasn't the default Azure Pipelines task for installing Python+pip. |
Yes, they don't work. I'll fix the commit message. Before we just used the python+pip that's installed on macOS, and now we'll be using one that Azure Pipelines can install, or rather it's there in a tools directory and some paths are updated by the "Use Python Version" task. |
Since #21722 we don't use the default macOS Python version. The problem is likely gone.
Since #21722 we don't use the default macOS Python version. The problem is likely gone.
Since #21722 we don't use the default macOS Python version. The problem is likely gone.
…'*' on macOS, a=testonly Automatic update from web-platform-tests [Azure Pipelines] stop setting no_proxy='*' on macOS (#23709) Since web-platform-tests/wpt#21722 we don't use the default macOS Python version. The problem is likely gone. -- wpt-commits: ab9402eb6a8e4ec5a7009a5d8d994a37615785a7 wpt-pr: 23709
…'*' on macOS, a=testonly Automatic update from web-platform-tests [Azure Pipelines] stop setting no_proxy='*' on macOS (#23709) Since web-platform-tests/wpt#21722 we don't use the default macOS Python version. The problem is likely gone. -- wpt-commits: ab9402eb6a8e4ec5a7009a5d8d994a37615785a7 wpt-pr: 23709
https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/tool/use-python-version?view=azure-devops
The default python/pip on the macOS VMs don't any longer. It may be
possible to fix this, but to fix the urgent issue use the method
that's supported by Azure Pipelines.
The python version will remain unchanged at 2.7.17, but pip will
change from 19.3.1 to 20.0.2.
pip_install.yml can be simplified because the remaining code path is
the same for macOS and Windows.
Fixes #21691.