[action] [PR:15352] update skip conditions for watermark cases #16297
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
Updated skip conditions of watermark cases.
QSharedWatermark: Queue watermark read on egress, since qos params are based on src, keep skipping lossless if src and dst's port_speed_cable_length different, or asic types(Q200, Q100) are different.
PgSharedWatermark: Unskip lossless multi_dut.
BufferPoolWatermark: The watermark is read on egress asic. Unskip lossy for multi_dut. Unskip lossless for multi_dut_shortlink_to_shortlink. Since qos params are based on src, keep skipping lossless if src and dst's port_speed_cable_length different, or asic types(Q200, Q100) are different.
Summary:
Fixes # (issue)
https://migsonic.atlassian.net/browse/MIGSMSFT-695 QoS SAI test gap review
Type of change
Back port request
Approach
What is the motivation for this PR?
update skip conditions for QSharedWatermark and PgSharedWatermark.
How did you do it?
How did you verify/test it?
Verified it on T2 testbed.
QSharedWatermark:
multi-dut short_to_short is also enabled, since ingress and egress port same config. Verification pending.
PgSharedWatermark multi_dut:
BufferPoolWatermark:
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation