-
Notifications
You must be signed in to change notification settings - Fork 727
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
Move skip check of test_passwd_hardening to tests_mark_conditions.yaml #6429
Conversation
Signed-off-by: Zhaohui Sun <zhaohuisun@microsoft.com>
@davidpil2002 Could you please take a look? Please let me know if you have any objection, thanks. |
tests_mark_conditions.yaml - this file is a configuration file or its require to add some code? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
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.
LGTM
tests_mark_conditions.yaml is a configuration file, test script or case will be skipped at the very beginning of test run, it doesn't have to run sanity check and other fixtures, it's best way to skip script or case. Because it will save us time to avoid running sanity check or other fixtures and also it could avoid the errors during these checks or fixtures. |
) What is the motivation for this PR? test_passw_hardening is unable to run on master image because sonic-net/sonic-buildimage#12138 hasn't been merged. But after running it on 202205 image which supports passw-harden(enabled in this PR sonic-net/sonic-buildimage#12025), found an issue and raised here sonic-net#6428. I think that it's better to skip test case in tests_mark_conditions.yaml instead of in test script. How did you do it? Move skip condition to tests_mark_conditions.yaml Add an issue in skip condition. After it's been fixed, we can run this script. How did you verify/test it? Run passw_hardening/test_passw_hardening.py Signed-off-by: Zhaohui Sun <zhaohuisun@microsoft.com>
) What is the motivation for this PR? test_passw_hardening is unable to run on master image because sonic-net/sonic-buildimage#12138 hasn't been merged. But after running it on 202205 image which supports passw-harden(enabled in this PR sonic-net/sonic-buildimage#12025), found an issue and raised here sonic-net#6428. I think that it's better to skip test case in tests_mark_conditions.yaml instead of in test script. How did you do it? Move skip condition to tests_mark_conditions.yaml Add an issue in skip condition. After it's been fixed, we can run this script. How did you verify/test it? Run passw_hardening/test_passw_hardening.py Signed-off-by: Zhaohui Sun <zhaohuisun@microsoft.com>
Signed-off-by: Zhaohui Sun zhaohuisun@microsoft.com
Description of PR
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
test_passw_hardening
is unable to run on master image because sonic-net/sonic-buildimage#12138 hasn't been merged.But after running it on 202205 image which supports passw-harden(enabled in this PR sonic-net/sonic-buildimage#12025), found an issue and raised here #6428.
I think that it's better to skip test case in tests_mark_conditions.yaml instead of in test script.
How did you do it?
How did you verify/test it?
Run passw_hardening/test_passw_hardening.py
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation