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
We are seeing the test is failing on some testbeds. There are two issues
The test is always using Ethernet0 for test. However, Ethernet0 is admin down on some HWSKU. Like topo_t0. On such devices, the pre_del_cnt and post_del_cnt are always 0, which cause the assert failure.
> pytest_assert(pre_del_cnt > post_del_cnt,
"Number of queue counters count differs from expected")
E Failed: Number of queue counters count differs from expected
The wait_until is not working perfectly as 60 seconds are not long enough for some low performance device. My suggestion is to change it to 120 seconds, and adding an assert to the result of wait_until like below
pytest_assert(wait_until(120, 20, 0, check_buffer_queues_cnt_cmd_output, ptfhost, gnxi_path,
dut_ip, iface_to_check, env.gnmi_port), "gnmi server not fully restarted")
Results you see
Test should pass consistently.
Results you expected to see
Test is flaky on some testbeds.
Is 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:
Issue Description
We are seeing the test is failing on some testbeds. There are two issues
Ethernet0
for test. However,Ethernet0
is admin down on some HWSKU. Like topo_t0. On such devices, thepre_del_cnt
andpost_del_cnt
are always0
, which cause the assert failure.wait_until
is not working perfectly as60
seconds are not long enough for some low performance device. My suggestion is to change it to120
seconds, and adding an assert to the result ofwait_until
like belowResults you see
Test should pass consistently.
Results you expected to see
Test is flaky on some testbeds.
Is 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: