Skip to content

Update qos sai tests due to splitting buffer queue configuration for lossy queue only device#18331

Merged
bingwang-ms merged 1 commit intosonic-net:masterfrom
JibinBao:update_qos_case_split_queue_buffer
Jun 4, 2025
Merged

Update qos sai tests due to splitting buffer queue configuration for lossy queue only device#18331
bingwang-ms merged 1 commit intosonic-net:masterfrom
JibinBao:update_qos_case_split_queue_buffer

Conversation

@JibinBao
Copy link
Copy Markdown
Contributor

@JibinBao JibinBao commented May 12, 2025

Description of PR

Update qos sai tests due to splitting buffer queue configuration for lossy queue only port. The design PR is: sonic-net/sonic-buildimage#22474

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • New Test case
    • Skipped for non-supported platforms
  • Test case improvement

Back port request

  • 202012
  • 202205
  • 202305
  • 202311
  • 202405
  • 202411

Approach

What is the motivation for this PR?

Update qos sai tests due to splitting buffer queue configuration for lossy queue only device

How did you do it?

Align qos sai tests according to the PR of sonic-net/sonic-buildimage#22474

How did you verify/test it?

Run the qos sai tests related to lossy queue.

Any platform specific information?

SN5610/SN5600/SN5640

Supported testbed topology if it's a new test case?

Documentation

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@JibinBao JibinBao changed the title Update qos sai tests due to splitting buffer queue configuration for lossy queue only port Update qos sai tests due to splitting buffer queue configuration for lossy queue only device May 12, 2025
@JibinBao JibinBao force-pushed the update_qos_case_split_queue_buffer branch from 617de4e to 8fe505b Compare May 12, 2025 02:05
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@JibinBao JibinBao force-pushed the update_qos_case_split_queue_buffer branch from 8fe505b to 48e986d Compare May 12, 2025 02:11
@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@bingwang-ms
Copy link
Copy Markdown
Collaborator

@kperumalbfn Could you help review?

@bingwang-ms
Copy link
Copy Markdown
Collaborator

@kperumalbfn Kindly reminder

@JibinBao
Copy link
Copy Markdown
Contributor Author

hi @bingwang-ms ,
Since @kperumalbfn has approved it, can you help merge it?

@bingwang-ms bingwang-ms merged commit 0084db2 into sonic-net:master Jun 4, 2025
14 checks passed
mssonicbld pushed a commit to mssonicbld/sonic-mgmt that referenced this pull request Jun 4, 2025
@mssonicbld
Copy link
Copy Markdown
Collaborator

Cherry-pick PR to 202505: #18804

@r12f
Copy link
Copy Markdown
Collaborator

r12f commented Aug 19, 2025

needed in 202412 but missing tags. fixing it.

@mssonicbld
Copy link
Copy Markdown
Collaborator

Cherry-pick PR to msft-202412: Azure/sonic-mgmt.msft#661

opcoder0 pushed a commit to opcoder0/sonic-mgmt that referenced this pull request Dec 8, 2025
…ic-net#18331)

Signed-off-by: opcoder0 <110003254+opcoder0@users.noreply.github.com>
AharonMalkin pushed a commit to AharonMalkin/sonic-mgmt that referenced this pull request Dec 16, 2025
gshemesh2 pushed a commit to gshemesh2/sonic-mgmt that referenced this pull request Dec 21, 2025
venu-nexthop pushed a commit to venu-nexthop/sonic-mgmt that referenced this pull request Jan 13, 2026
gshemesh2 pushed a commit to gshemesh2/sonic-mgmt that referenced this pull request Jan 26, 2026
ytzur1 pushed a commit to ytzur1/sonic-mgmt that referenced this pull request Feb 2, 2026
venu-nexthop pushed a commit to venu-nexthop/sonic-mgmt that referenced this pull request Mar 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants