Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make test_idf_isolated_withdraw_all more robust #16271

Merged
merged 1 commit into from
Jan 4, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions tests/bgp/test_seq_idf_isolation.py
Original file line number Diff line number Diff line change
Expand Up @@ -167,9 +167,9 @@ def test_idf_isolated_withdraw_all(duthosts, rand_one_downlink_duthost,
# Verify DUT is in isolated-withdraw-all state.
pytest_assert(IDF_ISOLATED_WITHDRAW_ALL == get_idf_isolation_state(duthost),
"DUT is not in isolated_withdraw_all state")
pytest_assert(verify_only_loopback_routes_are_announced_to_neighs(duthosts, duthost, nbrs,
traffic_shift_community),
"Failed to verify only loopback route in isolated_withdraw_all state")
if not wait_until(60, 3, 0, verify_only_loopback_routes_are_announced_to_neighs,
duthosts, duthost, nbrs, traffic_shift_community):
pytest.fail("Failed to verify only loopback route in isolated_withdraw_all state")
finally:
# Recover to unisolated state
duthost.shell("sudo idf_isolation unisolated")
Expand Down
Loading