From 60d9881e35c3c5786b9f52f7a8f44aefbb30a6b4 Mon Sep 17 00:00:00 2001 From: Kevin Wang Date: Fri, 20 Aug 2021 17:19:40 +0800 Subject: [PATCH] [test_heartbeat_failure] skip the heartbeat test What is the motivation for this PR? After this test is failed, then the subsequent dual-tor test cases will mostly fail as well. Need to figure out the reason why can't gurantee all interfaces to be toggled to active state. See detail on issue#8423. How did you do it? just skip this test before issue is addressed. Signed-off-by: Kevin Wang --- tests/dualtor/test_heartbeat_failure.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/tests/dualtor/test_heartbeat_failure.py b/tests/dualtor/test_heartbeat_failure.py index 2db9bc6a3ac..058272b02a5 100644 --- a/tests/dualtor/test_heartbeat_failure.py +++ b/tests/dualtor/test_heartbeat_failure.py @@ -11,7 +11,8 @@ from tests.common.dualtor.constants import MUX_SIM_ALLOWED_DISRUPTION_SEC pytestmark = [ - pytest.mark.topology("dualtor") + pytest.mark.topology("dualtor"), + pytest.mark.skip(reason="skipping until the mux toggle issue is addressed") ]