Skip to content

add support for different dualtor-aa topologies for test_qos_sai.py#19317

Open
CharudattaSChitale wants to merge 1 commit intosonic-net:masterfrom
CharudattaSChitale:qos-support-dualtor-aa
Open

add support for different dualtor-aa topologies for test_qos_sai.py#19317
CharudattaSChitale wants to merge 1 commit intosonic-net:masterfrom
CharudattaSChitale:qos-support-dualtor-aa

Conversation

@CharudattaSChitale
Copy link
Contributor

What is the motivation for this PR?
This PR enables qos/test_qos_sai.py on all dualtor-aa topologies.
Till now, we have been enabling qos/test_qos_sai.py on different dualtor-aa topologies as and when we use it.
Its better to enable all in one go

How did you do it?
Added dualtor-aa-120, dualtor-aa-56, dualtor-aa-64, dualtor-aa-64-breakout to supported topologies for qos_sai.

Type of change
-Test modification

Back port request
-202411
-202505

How did you verify/test it?
Made sure that after making these changes, qos_sai TCs ran on dualtor-aa-64-breakout testbed

@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

Azure Pipelines will not run the associated pipelines, because the pull request was updated after the run command was issued. Review the pull request again and issue a new run command.

kazinator-arista pushed a commit to kazinator-arista/sonic-mgmt that referenced this pull request Mar 4, 2026
…tomatically (sonic-net#19317)

src/sonic-linux-kernel

* 58d3bf5 - (HEAD -> 202205, origin/202205) [ci] Migrate to sonicbld1es agent pool. (sonic-net#397) (4 weeks ago) [Liu Shilong]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants