-
Notifications
You must be signed in to change notification settings - Fork 740
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
Cisco-8000 test pfcwd function background traffic revision #15772
Cisco-8000 test pfcwd function background traffic revision #15772
Conversation
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.
Pinged Kevin/Storm to back port the pr 14711 to 202405
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
Cherry-pick PR to 202405: #15841 |
Hi @rraghav-cisco, this could be the potential issue for pfc_function that failed in having pfcwd storm detection step and still send out packet in verify_tx_egress. Could you have a look please. |
Description of PR
Summary:
Type of change
Back port request
Related PRs
#14711 is not in 202405, but is requested for the branch. Without that PR in 202405, the double commit of this PR will have a either have a merge conflict or possibly fail if it happens to not conflict. Possible to get that PR in 202405?
Approach
What is the motivation for this PR?
Fix flaky test on Cisco-8000.
Clarify exceptions that do occur for all vendors.
How did you do it?
How did you verify/test it?
Verified pass 10 times on Cisco-8122 T0 on 202405 branch. But master/202405 aren't in sync yet due to missing 14711 PR.
Any platform specific information?
The verify_tx_egress change is cisco-only.
The exception catcher removal should improve exception readability for all vendors.
Supported testbed topology if it's a new test case?
Documentation