Change run_tests.sh to support non-venv Python3 environment #8828
+3
−372
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
|
/azp run |
|
No commit pushedDate could be found for PR 8828 in repo sonic-net/sonic-mgmt |
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.
Description of PR
Summary:
In this PR, run_tests.sh will use non-venv Python3 in sonic-mgmt-docker.
Before this PR, sonic-mgmt-docker is modified to add Python3 packages to non-venv environment. (sonic-net/sonic-buildimage#15726)
After this PR, sonic-mgmt master branch will always use Python3 for all testcases.
For 202205 and 202012 branch, sonic-mgmt will still use Python2 for all testcases.
Type of change
Back port request
Approach
What is the motivation for this PR?
This is part of Python3 migration in sonic-mgmt-docker.
How did you do it?
Change run_tests.sh to support non-venv Python3 environment
How did you verify/test it?
Test with physical testbed.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation