Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix flakiness of qos/test_qos_dscp_mapping.py (#13496)
What is the motivation for this PR? In some of the cases, after sending packets (2000) the queue counter value is not reflecting correct value (counter value is less than expected) and thus lead to test failure. In the issue state, reading the counter value (in breakpoint) again shows the correct value. Sample output in failure case: 3238 " Inner Packet DSCP Value Expected Egress Queue Egress Queue Count Result Actual Egress Queue\n", 3239 "------------------------- ----------------------- -------------------- -------------------------------- ---------------------\n", 3240 " 0 1 865 FAILURE - DUT POLL FAILURE -1\n", 3241 " 1 1 2000 SUCCESS 1\n", 3242 " 2 1 1022 FAILURE - DUT POLL FAILURE -1\n", 3243 " 3 3 2000 SUCCESS 3\n", 3244 " 4 4 1396 FAILURE - DUT POLL FAILURE -1\n", 3245 " 5 1 2000 SUCCESS 1\n", 3246 " 6 1 1449 FAILURE - DUT POLL FAILURE -1\n", 3247 " 7 1 2000 SUCCESS 1\n", 3248 " 8 0 1909 FAILURE - INCORRECT PACKET COUNT 0\n", 3249 " 9 1 2000 SUCCESS 1\n", ... How did you do it? Updated the test to wait for atleast 10s (which is hardware counter polling time) before reading the queue counters. $ counterpoll show | grep -i queue_stat QUEUE_STAT default (10000) enable Updated the logic to re-poll the counters if the egress packet count is not as expected. How did you verify/test it? Stressed the test with fix on Arista-7260CX3-D108C8. Test is passing consistently with the fix.
- Loading branch information