[action] [PR:21617] Enhance PTF function at scale testbed#945
Merged
mssonicbld merged 1 commit intoAzure:202412from Jan 4, 2026
Merged
[action] [PR:21617] Enhance PTF function at scale testbed#945mssonicbld merged 1 commit intoAzure:202412from
mssonicbld merged 1 commit intoAzure:202412from
Conversation
<!-- Please make sure you've read and understood our contributing guidelines; https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md Please provide following information to help code review process a bit easier: --> ### Description of PR On Scale testbed there are 2 main differences: 1. There are much more PTF ports 2. There are much more OVS and interface configurations Those lead to: 1. NIC would take more time to handle the receiving packets 2. PTF could take more time to process As a result: 1. More time to spend in ptf function testutils.verify_packet Summary: Fixes # (issue) ### Type of change <!-- - Fill x for your type of change. - e.g. - [x] Bug fix --> - [ ] Bug fix - [ ] Testbed and Framework(new/improvement) - [ ] New Test case - [ ] Skipped for non-supported platforms - [ ] Test case improvement ### Back port request - [ ] 202205 - [ ] 202305 - [ ] 202311 - [ ] 202405 - [ ] 202411 - [ ] 202505 - [x] 202511 ### Approach #### What is the motivation for this PR? To increase the PTF traffic handling stability in the scale testbed #### How did you do it? Add more wait time in ptf function testutils.verify_packet #### How did you verify/test it? Run it in the local scale testbed #### Any platform specific information? #### Supported testbed topology if it's a new test case? ### Documentation <!-- (If it's a new feature, new test case) Did you update documentation/Wiki relevant to your implementation? Link to the wiki page? -->
Collaborator
Author
|
Original PR: sonic-net/sonic-mgmt#21617 |
Collaborator
Author
|
/azp run |
12 tasks
|
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
1 participant
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
On Scale testbed there are 2 main differences:
Those lead to:
As a result:
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
To increase the PTF traffic handling stability in the scale testbed
How did you do it?
Add more wait time in ptf function testutils.verify_packet
How did you verify/test it?
Run it in the local scale testbed
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation