Disable ipv6 traffic from ptf to dut for two qos cases because it will introduce noise#20416
Merged
roy-sror merged 2 commits intosonic-net:masterfrom Oct 28, 2025
Merged
Conversation
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
JibinBao
force-pushed
the
qos_disable_ipv6_traffic
branch
from
0ebb0ca to
c57abc2
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
JibinBao
changed the title
JibinBao
force-pushed
the
qos_disable_ipv6_traffic
branch
from
c57abc2 to
ea5ea4d
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run Azure.sonic-mgmt |
Collaborator
|
/AzurePipelines run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run Azure.sonic-mgmt |
Collaborator
|
/AzurePipelines run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run Azure.sonic-mgmt |
Collaborator
|
/AzurePipelines run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Contributor
Author
|
/azpw run Azure.sonic-mgmt |
Collaborator
|
/AzurePipelines run Azure.sonic-mgmt |
|
Azure Pipelines successfully started running 1 pipeline(s). |
nhe-NV
approved these changes
Aug 29, 2025
When IPv6 is not enabled on the PTF, it sends RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied. Since the PTF sends RS packets randomly, the tests for `testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy]` and `testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy]` fail intermittently.
Please enter the commit message for your changes. Lines starting
JibinBao
force-pushed
the
qos_disable_ipv6_traffic
branch
from
ea5ea4d to
2378480
Compare
Collaborator
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
roy-sror
approved these changes
Oct 28, 2025
dcaugher
pushed a commit
to dcaugher/sonic-mgmt
that referenced
this pull request
Nov 12, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases.
dcaugher
pushed a commit
to dcaugher/sonic-mgmt
that referenced
this pull request
Nov 12, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases.
vikumarks
pushed a commit
to vikumarks/sonic-mgmt
that referenced
this pull request
Dec 1, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: vikumarks <[email protected]>
albertovillarreal-keys
pushed a commit
to albertovillarreal-keys/sonic-mgmt
that referenced
this pull request
Dec 2, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Alberto Villarreal <[email protected]>
opcoder0
pushed a commit
to opcoder0/sonic-mgmt
that referenced
this pull request
Dec 8, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: opcoder0 <[email protected]>
selldinesh
pushed a commit
to selldinesh/sonic-mgmt
that referenced
this pull request
Dec 11, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: selldinesh <[email protected]>
echuawu
pushed a commit
to echuawu/sonic-mgmt
that referenced
this pull request
Dec 12, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases.
saravanan-nexthop
pushed a commit
to saravanan-nexthop/sonic-mgmt
that referenced
this pull request
Dec 15, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Saravanan <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Guy Shemesh <[email protected]>
AharonMalkin
pushed a commit
to AharonMalkin/sonic-mgmt
that referenced
this pull request
Dec 16, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Aharon Malkin <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Dec 21, 2025
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Guy Shemesh <[email protected]>
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Jan 13, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases.
yifan-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Jan 14, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: YiFan Wang <[email protected]>
gshemesh2
pushed a commit
to gshemesh2/sonic-mgmt
that referenced
this pull request
Jan 26, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Guy Shemesh <[email protected]>
lakshmi-nexthop
pushed a commit
to lakshmi-nexthop/sonic-mgmt
that referenced
this pull request
Jan 28, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Lakshmi Yarramaneni <[email protected]>
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Jan 29, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases.
ytzur1
pushed a commit
to ytzur1/sonic-mgmt
that referenced
this pull request
Feb 2, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Yael Tzur <[email protected]>
abhishek-nexthop
pushed a commit
to nexthop-ai/sonic-mgmt
that referenced
this pull request
Feb 6, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases.
rraghav-cisco
pushed a commit
to rraghav-cisco/sonic-mgmt
that referenced
this pull request
Feb 13, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases. Signed-off-by: Raghavendran Ramanathan <[email protected]>
kazinator-arista
pushed a commit
to kazinator-arista/sonic-mgmt
that referenced
this pull request
Mar 4, 2026
…D automatically (sonic-net#20416) #### Why I did it src/sonic-platform-daemons ``` * 10ef649 - (HEAD -> 202311, origin/202311) Improve parsing of media-settings.json for non-CMIS and breakout ports (sonic-net#533) (sonic-net#545) (9 hours ago) [longhuan-cisco] ``` #### How I did it #### How to verify it #### Description for the changelog
venu-nexthop
pushed a commit
to venu-nexthop/sonic-mgmt
that referenced
this pull request
Mar 27, 2026
…l introduce noise (sonic-net#20416) When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy] and testQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy] fail intermittently. To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases.
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
4 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
When IPv6 is enabled on the PTF, PTF will send RS packets with DSCP 0, which corresponds to PG 1. Consequently, if we test PG 0, the PG watermark is affected because some part of the egress port buffer is occupied for TC 1. Since the PTF sends RS packets randomly, the tests for
testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy]andtestQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy]fail intermittently.To stabilize the cases, we disable the ipv6 traffic from ptf to dut for the two cases.
Summary:
Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Stabilize
testQosSaiPgSharedWatermark[single_asic-wm_pg_shared_lossy]andtestQosSaiQSharedWatermark[single_asic-wm_q_shared_lossy]How did you do it?
Disable the ipv6 traffic from ptf to dut for the two cases.
How did you verify/test it?
Run the two case many times
Any platform specific information?
Any
Supported testbed topology if it's a new test case?
Documentation