Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Cherry-pick] Adding COUNTER_MARGIN to Ingress drop counters …#9896 #10210

Merged
merged 1 commit into from
Oct 19, 2023

Conversation

ansrajpu-git
Copy link
Contributor

…for qos tests (#9896)

  • Qos_LossyQueueTest fix_adding COUNTER MARGIN

  • Adding COUNTER_MARGIN to qos PFCXonTest

  • Adding COUNTER_MARGIN to qos PFCTest

  • testQosSaiPFCXoffLimit updated with correct check

  • Conditional check corrected for LossyQueueTest

Description of PR

Master branch PR #9896

Summary:
Fixes # (issue)

Type of change

  • Bug fix
  • Testbed and Framework(new/improvement)
  • Test case(new/improvement)

Back port request

  • 201911
  • 202012
  • 202205

Approach

What is the motivation for this PR?

How did you do it?

How did you verify/test it?

Any platform specific information?

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

Documentation

…for qos tests (sonic-net#9896)

* Qos_LossyQueueTest fix_adding COUNTER MARGIN

* Adding COUNTER_MARGIN to qos PFCXonTest

* Adding COUNTER_MARGIN to qos PFCTest

* Flake8 fixes

* testQosSaiPFCXoffLimit updated with correct check

* Conditional check corrected for LossyQueueTest

* flake8 fix
@abdosi
Copy link
Contributor

abdosi commented Oct 4, 2023

@vmittal-msft please help review,

@ansrajpu-git
Copy link
Contributor Author

@vmittal-msft, could you please review this PR?

@wangxin wangxin merged commit 4adc032 into sonic-net:202205 Oct 19, 2023
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

5 participants