-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
regression test for exponential recursion bug on CRDs #111912
regression test for exponential recursion bug on CRDs #111912
Conversation
Please note that we're already in Test Freeze for the Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Thu Aug 18 13:40:40 UTC 2022. |
/sig api-machinery |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aojea 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 |
/assign @liggitt the test flakes with
|
) | ||
|
||
// Regression test for https://issues.k8s.io/109099 | ||
func TestCRDExponentialRecursionBug(t *testing.T) { |
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.
Should we turn that into a benchmark? It's unclear since I don't think benchmarks are run or that we have a good way to see the results.
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.
The way I've seen benchmarks used in k/k is adding the results to the commit description or as a comment, but AFAIK they don't run on CI , I remember this was discussed but don't know what was the conclusion, maybe @BenTheElder remember something more
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.
Yeah, we're automatically running some benchmarks in the smd repository but I don't think we have the same thing in k/k.
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.
we don't run them in K/K historically because we had major noisy neighbor problems in CI.
it still may be worth checking in benchmarks to avoid needing to reimplement for future sensitive changes / debugging?
it may also not be a big issue now if running in sig-k8s-infra cluster where we require jobs to at least set cpu/memory requests now (though disk I/O noise is still unavoidable #3595)
/triage accepted |
6419315
to
8d7264f
Compare
/hold cancel This is ok now |
/lgtm non-blocking for 1.25, can merge to 1.26 |
…2-upstream-release-1.25 Automated cherry pick of #111912: regression test for exponential recursion bug on CRDs
/kind regression
Special notes for your reviewer:
Regression test for bug #109099