-
Notifications
You must be signed in to change notification settings - Fork 741
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
Porting 15718 to 202405: Adding a fixture to set scheduler to slower speeds and revert it back. #16199
base: 202405
Are you sure you want to change the base?
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @rraghav-cisco , could you please paste the test result with the code that resolved the conlficts? |
Hi @yejianquan , I am seeing pass in Dwrr, but fails in DwrrWeightChange:
|
@rraghav-cisco is DwrrWeightChange because of the testbed issue or the script? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Hi @rraghav-cisco , this new test failed on T0/T1 setup #16314. could you please fix it ASAP? |
convert to draft because it fails on t0/t1 cisco devices #16314 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pls fix the error on t0/t1 as well.
@rraghav-cisco can you include fix #16315 in this PR? |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
@sdszhang , done. |
@yejianquan : The issue was in my workspace. After fixing the workspace, all of these passed. |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Description of PR
Summary:
Fixes the flakiness of DWRR testcase. The PR adds a new fixture that slows down the scheduler without changing the underlying algorithm. This allows the dWRR test to pass consitently.
Type of change
Back port request
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