-
Notifications
You must be signed in to change notification settings - Fork 763
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
[test_system_health.py] Adjust test cases of system health #4562
Conversation
Change-Id: I01710a47112b483fbedc5d0ff83b70bed5c44c70
Change-Id: Idd1ca2133593c45ce18de0e82a40281ab557561d
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@lguohan should we fix "monit summary -B"? |
|
||
critical_process = random.sample(running_critical_process, 1)[0] | ||
with ProcessExitContext(duthost, container, critical_process): | ||
time.sleep(DEFAULT_INTERVAL) |
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.
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.
System-health poll critical process status every 60 seconds, so it has to wait 60 second here.
@@ -348,3 +369,18 @@ def __exit__(self, exc_type, exc_val, exc_tb): | |||
:return: | |||
""" | |||
self.dut.command('mv -f {} {}'.format(self.backup_config, self.origin_config)) | |||
|
|||
|
|||
class ProcessExitContext: |
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.
@qiluo-msft could you please approve and sign off? |
…#4562) What is the motivation for this PR? Command monit summary -B can no longer display the status for each critical process, system-health should not depend on it and need find a way to monitor the status of critical processes. The PR is to adjust the test case and cover the change. How did you do it? Adjust test case to check critical process without monit Stop a critical process and check system-health status How did you verify/test it? Run the regression
Depends on sonic-net/sonic-buildimage#9068
Change-Id: I01710a47112b483fbedc5d0ff83b70bed5c44c70
Description of PR
Summary:
Command monit summary -B can no longer display the status for each critical process, system-health should not depend on it and need find a way to monitor the status of critical processes. The PR is to adjust the test case and cover the change.
Type of change
Back port request
Approach
What is the motivation for this PR?
Command monit summary -B can no longer display the status for each critical process, system-health should not depend on it and need find a way to monitor the status of critical processes. The PR is to adjust the test case and cover the change.
How did you do it?
How did you verify/test it?
Run the regression
Any platform specific information?
N/A
Supported testbed topology if it's a new test case?
N/A
Documentation