Correctly pass --py2 or --py3 to some Azure Pipeline tasks #27199
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We had incorrectly assumed that all Azure Pipeline VMs had access to Python 2, but that isn't true (the Edge run VMs only have Py3 nowadays). As such, update_hosts.yml and update_manifest.yml broke on those VMs. Instead, make the pyflag a variable for those yml files and set it appropriately.
foolip
approved these changes
Jan 15, 2021
|
Infra failure on taskcluster is unrelated, see #27200 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had incorrectly assumed that all Azure Pipeline VMs had access to
Python 2, but that isn't true (the Edge run VMs only have Py3 nowadays).
As such, update_hosts.yml and update_manifest.yml broke on those VMs.
Instead, make the pyflag a variable for those yml files and set it
appropriately.