Skip to content

Commit 12b7793

Browse files
StormLiangMSmssonicbld
authored andcommitted
[XFAIL: test_crm_available.py] set xfail of test_crm_available on dualtor platform (#18874)
What is the motivation for this PR? To xfail test_crm_available, which has a known issue on broadcom dualtor platform. How did you do it? Add xfail in tests_mark_conditions.yaml How did you verify/test it? Run test on dualtor platform =================================================================================================================== short test summary info ==================================================================================================================== XFAIL crm/test_crm_available.py::test_crm_next_hop_group[bjw-can-7260-16-None] - There is a known issue with broadcom dualtor Any platform specific information? Broadcom dualtor platform
1 parent ab5fd70 commit 12b7793

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

tests/common/plugins/conditional_mark/tests_mark_conditions.yaml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -294,6 +294,12 @@ crm/test_crm.py::test_crm_fdb_entry:
294294
conditions:
295295
- "'t0' not in topo_name and topo_type not in ['m0', 'mx']"
296296

297+
crm/test_crm_available.py:
298+
xfail:
299+
reason: "There is a known issue with broadcom dualtor"
300+
conditions:
301+
- "https://github.com/sonic-net/sonic-mgmt/issues/18873 and 'dualtor' in topo_name and asic_type in ['broadcom']"
302+
297303
#######################################
298304
##### decap #####
299305
#######################################

0 commit comments

Comments
 (0)