Fix bug which hangs the test if warmboot has an issue #2994
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: Fix the test bug which hangs the test execution, if warmboot has an issue (either in shutdown or boot-up path).
Fixes # (issue)
Type of change
Approach
Replace the
duthost.get_up_time()
withduthost.get_now_time()
This change is needed as the duthost.get_up_time() call always returns the same value (the time since the DUT was last UP).
As a result, the
time_passed
value always remains a constant int.With
get_now_time
,time_passed
gets updated every iteration, and the loop exits when timout occurs.What is the motivation for this PR?
How did you do it?
How did you verify/test it?
Tested on a DUT where the issue was seen:
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation