Skip to content

Comments

[action] [PR:22259] Change dummy ip for fill packets to eliminate false positives#22474

Merged
mssonicbld merged 1 commit intosonic-net:202511from
mssonicbld:cherry/202511/22259
Feb 20, 2026
Merged

[action] [PR:22259] Change dummy ip for fill packets to eliminate false positives#22474
mssonicbld merged 1 commit intosonic-net:202511from
mssonicbld:cherry/202511/22259

Conversation

@mssonicbld
Copy link
Collaborator

Description of PR

Summary:
Fixes # (issue)

Type of change

  • 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
  • 202412
  • 202505
  • 202511

Approach

What is the motivation for this PR?

We were seeing failures in packet trimming tests when verifying UDP packets. This is because the shaper on TH5 is still sending a few packets a second that were used to fill up the buffer (simulating congestion) and these packets are nearly identical to the UDP packets used to verify trimming. This is leading to false positives where a packet that was used to fill the buffer is being detected as a "trimmed" packet when packet trimming is turned off.

How did you do it?

Fixed this by changing the dummy ip for the packets used to fill the buffer, meaning they won't be mistaken for a packet that the test sends to verify trimming.

How did you verify/test it?

Verified that the failure goes away with the change.

Any platform specific information?

Supported testbed topology if it's a new test case?

Documentation

…net#22259)

What is the motivation for this PR?
We were seeing failures in packet trimming tests when verifying UDP packets. This is because the shaper on TH5 is still sending a few packets a second that were used to fill up the buffer (simulating congestion) and these packets are nearly identical to the UDP packets used to verify trimming. This is leading to false positives where a packet that was used to fill the buffer is being detected as a "trimmed" packet when packet trimming is turned off.

How did you do it?
Fixed this by changing the dummy ip for the packets used to fill the buffer, meaning they won't be mistaken for a packet that the test sends to verify trimming.

How did you verify/test it?
Verified that the failure goes away with the change.

Signed-off-by: Ryan Garofano <rgarofano@arista.com>
Signed-off-by: mssonicbld <sonicbld@microsoft.com>
@mssonicbld
Copy link
Collaborator Author

Original PR: #22259

@mssonicbld
Copy link
Collaborator Author

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mssonicbld mssonicbld merged commit 2759955 into sonic-net:202511 Feb 20, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants