Define seastone watchdog too_big_timeout to fix platform issue#1
Open
celestica-gl wants to merge 19 commits intoSONIC-DEV:masterfrom
Open
Define seastone watchdog too_big_timeout to fix platform issue#1celestica-gl wants to merge 19 commits intoSONIC-DEV:masterfrom
celestica-gl wants to merge 19 commits intoSONIC-DEV:masterfrom
Conversation
TODO: warm-reboot need fix ssh login ptfhost error
TODO: warm-reboot need fix ssh login ptfhost error
1: fix t0, t1, add-topo add-vm error 2: add pdu support on testbed
stage version which could run full pytest
feat:Seastone2 adaptation
fix e1031 t0 testbed config issues
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Summary:
Fixes watchdog platform testbed test case too_big_timeout issue.
Type of change
Add the definiation of too_big_timeout value in watchdog.yml which will be used to compare to the seastone watchdog max time setting.
How did you do it?
1 Add the definiation of too_big_timeout value in watchdog.yml which will be used to compare to the seastone watchdog max time setting.
2 Add the too_big_timeout checking in watchdog.py of seastone DUT platform definiation.
If the too_big_timeout value is bigger than the watchdog max time setting value, test case will return Error which is expected test result.
How did you verify/test it?
Through running Testbed pytest platform watchdog test case.
Any platform specific information?
celestica seastone-r0 platform
Supported testbed topology if it's a new test case?
yes.