[Bug]: [dualtor_io] test_tor_bgp_failure.py fails to run on kvm testbed #16448
Assignees
Comments
12 tasks
wangxin
pushed a commit
that referenced
this issue
Jan 13, 2025
What is the motivation for this PR? The script dualtor_io/test_tor_bgp_failure.py has recently been failing frequently on the KVM testbed. This issue is being tracked in #16448. As a temporary measure, we have applied a conditional mark to skip this test in PR checks. How did you do it? As a temporary measure, we have applied a conditional mark to skip this test in PR checks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
Recently, script
dualtor_io/test_tor_bgp_failure.pyfails to run on kvm testbed with high probability, and each retry will take around one hour. Please take a look.https://elastictest.org/scheduler/testplan/678053fa572c09d3aa482338?testcase=dualtor_io%2Ftest_tor_bgp_failure.py%7C%7C%7C1&type=console
Results you see
=========================== short test summary info ============================
DEBUG:tests.conftest:[log_custom_msg] item: <Function test_active_tor_shutdown_bgp_sessions_downstream[active-active]>
INFO:root:Can not get Allure report URL. Please check logs
SKIPPED [1] dualtor_io/test_tor_bgp_failure.py:80: Skip cable type 'active-active'
SKIPPED [1] dualtor_io/test_tor_bgp_failure.py:102: Skip cable type 'active-active'
SKIPPED [1] dualtor_io/test_tor_bgp_failure.py:123: Skip cable type 'active-active'
SKIPPED [1] dualtor_io/test_tor_bgp_failure.py:145: Skip cable type 'active-active'
SKIPPED [1] dualtor_io/test_tor_bgp_failure.py:167: Skip as no mux ports of 'active-active' cable type
SKIPPED [1] dualtor_io/test_tor_bgp_failure.py:211: Skip cable type 'active-standby'
SKIPPED [1] dualtor_io/test_tor_bgp_failure.py:211: Skip as no mux ports of 'active-active' cable type
ERROR dualtor_io/test_tor_bgp_failure.py::test_active_tor_shutdown_bgp_sessions_downstream[active-active]
!!!!!!!!!!!!!!!!!!!!!!!!!! stopping after 1 failures !!!!!!!!!!!!!!!!!!!!!!!!!!!
======= 5 passed, 7 skipped, 13 warnings, 1 error in 3382.86s (0:56:22) ========
Results you expected to see
It should be stable to run on kvm testbed.
Is it platform specific
generic
Relevant log output
No response
Output of
show versionNo response
Attach files (if any)
No response
The text was updated successfully, but these errors were encountered: