You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
======================================================================
FAIL: sai_qos_tests.PGSharedWatermarkTest
----------------------------------------------------------------------
Traceback (most recent call last):
File "saitests/py3/sai_qos_tests.py", line 4623, in runTest
* (packet_length + internal_hdr_size)))
AssertionError
----------------------------------------------------------------------
Ran 1 test in 934.434s
The issue appears to be during the dynamically_compensate_leakout Compensate 2176538 packets to port 34, and retry 1 times
We can see this is sending far too many packets 2176538.
Issue Description
Failure seen:
The issue appears to be during the
dynamically_compensate_leakout
Compensate 2176538 packets to port 34, and retry 1 times
We can see this is sending far too many packets
2176538
.This function compares the
TX_OK
value before and after sending the 41 packets.Here is where it stores the counts before the packets are sent:
https://github.com/sonic-net/sonic-mgmt/blob/202405/tests/saitests/py3/sai_qos_tests.py#L4464
And within
dynamically_compensate_leakout
here is where they are read:https://github.com/sonic-net/sonic-mgmt/blob/202405/tests/saitests/py3/sai_qos_tests.py#L454
The problem here is the call to
dynamically_compensate_leakout
is passedself.src_client
as thethrift_client
argument but is operating on a port in theself.dst_client
:https://github.com/sonic-net/sonic-mgmt/blob/202405/tests/saitests/py3/sai_qos_tests.py#L4551
In this failure case I can see that the
dst_port_id
value is used on both asics:If I dump the
TX_OK
of port 32 on the src asic I get:On the dst asic I get:
This is where the massive compensate packet number comes from:
Results you see
We poll the incorrect asic/dut client in
dynamically_compensate_leakout
Results you expected to see
We should poll the same asic/dut client in
dynamically_compensate_leakout
as the port we're referencingIs it platform specific
generic
Relevant log output
No response
Output of
show version
No response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered: