[action] [PR:12178] Add more information log in pfcwd accuracy case for further debug#13963
Merged
mssonicbld merged 1 commit intosonic-net:202405from Aug 3, 2024
Merged
Conversation
…nic-net#12178) What is the motivation for this PR? The test_pfcwd_timer_accuracy failed due to "Failed: Real detection time is greater than configured: Real detect time: 1015 Expected: 800 (wd_detect_time + wd_poll_time)" How did you do it? Add more information in the log, to monitor the status if hit the issue during the nightly build. How did you verify/test it? Locally run
8 tasks
Collaborator
Author
|
Original PR: #12178 |
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
2 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.
Description of PR
Summary:
Fixes # (issue)
27262192
Type of change
Back port request
Approach
What is the motivation for this PR?
The test_pfcwd_timer_accuracy failed due to "Failed: Real detection time is greater than configured: Real detect time: 1015 Expected: 800 (wd_detect_time + wd_poll_time)"
How did you do it?
Add more information in the log, to monitor the status if hit the issue during the nightly build.
How did you verify/test it?
Locally run
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation