[action] [PR:15772] Cisco-8000 test pfcwd function background traffic revision#15841
Merged
mssonicbld merged 1 commit intosonic-net:202405from Dec 11, 2024
Merged
Conversation
8 tasks
Collaborator
Author
|
Original PR: #15772 |
Contributor
|
Do not merge, this will cause a test failure in 202405 for cisco without #14711. |
Contributor
|
Hi @rbpittman please confirm if this is ready to merge |
8 tasks
Contributor
|
@auspham This is not ready to merge. |
8 tasks
Contributor
|
Hi @rbpittman i have merged #14711 for you. I'll retrigger this CI, Meanwhile could you please help confirming if it should be okay to merge now. |
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
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
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:
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