-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Tweak up flaking end-to-end tests of API Priority and Fairness #96874
Tweak up flaking end-to-end tests of API Priority and Fairness #96874
Conversation
/cc @yue9944882 |
/uncc @smarterclayton |
/retest |
your four commits LGTM, do you want to rebase on top of Min's latest commit? (I think Min has incorporated your review, so one of your commits might be redundant when you rebase) |
f045377
to
e7b0f58
Compare
/retest |
/lgtm |
BTW, |
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
/triage accepted |
{username: "highqps", qps: 100.0, concurrencyMultiplier: 2.0}, | ||
{username: "lowqps", qps: 5.0, concurrencyMultiplier: 0.5}, | ||
{username: highQPSClientName, qps: 90, concurrencyMultiplier: 2.0, expectedCompletedPercentage: 0.90}, | ||
{username: lowQPSClientName, qps: 4, concurrencyMultiplier: 0.5, expectedCompletedPercentage: 0.90}, |
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.
Isn't this .9 an increase over #96798's .75?
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.
A recent failure:
Dec 4 15:38:28.824: client "highqps-apf-8126": got 36.6% completed requests, want at least 75.0%
So I think we'll need a followup.
Perhaps we need to use quite large share amounts to throttle the rest of the cluster.
/milestone v1.20 |
/approve Multiple reviewers seem to think this will help so let's merge it--I don't quite understand but I don't want to block this. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lavalamp, MikeSpreitzer The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Review the full test history for this PR. Silence the bot with an |
Hey there, just wanted to mention that this was after test freeze and the branch cut. If you’d like this in 1.20, it needs to be cherry picked and the release is tomorrow so this probably won’t make it until 1.20.1. |
The tests have been disabled in 1.20 (#97075), so I don't think it matters too much whether or not we cherry-pick this. |
What type of PR is this?
/kind bug
/kind flake
What this PR does / why we need it:
This builds on #96798 by reducing the expected throughput, since the main problem seems to be that the expected throughput is sometimes not achieved.
Which issue(s) this PR fixes:
Fixes #96710
Special notes for your reviewer:
As noted in my comments on #96798, I think the tests here need deep revision in order to become good tests; this PR is a tactical fix to stop the flakes.
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: