Skip to content

Commit 4aaaf52

Browse files
StormLiangMSmssonicbld
authored andcommitted
[XFAIL: test_crm_available.py] set xfail of test_crm_available on dualtor platform (sonic-net#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 ead048e commit 4aaaf52

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

tests/common/plugins/conditional_mark/tests_mark_conditions.yaml

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

355+
crm/test_crm_available.py:
356+
xfail:
357+
reason: "There is a known issue with broadcom dualtor"
358+
conditions:
359+
- "https://github.com/sonic-net/sonic-mgmt/issues/18873 and 'dualtor' in topo_name and asic_type in ['broadcom']"
360+
355361
#######################################
356362
##### dash #####
357363
#######################################

0 commit comments

Comments
 (0)