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
[Flaking Test] UT TestSchedulerGuaranteeNonNilNodeInSchedulingCycle #124591
Comments
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
+1 The default length of fake watcher's chan is only 100, which affects the performance a little. If the obj of chan is not consumed in time, it will cause panic. Should the length be made configurable? kubernetes/staging/src/k8s.io/apimachinery/pkg/watch/watch.go Lines 51 to 53 in 7947052
kubernetes/staging/src/k8s.io/apimachinery/pkg/watch/watch.go Lines 266 to 277 in 7947052
|
In my tests, if I change |
Is this a real problem in production or only in CI? |
It's a flaky test but impacted a lot of staging codes if we want to change the size dynamically or make it a blocking watcher, let me see how to solve this elegantly. |
But curious about why this start to be flaky, scheduler becomes slower? |
Didn't find more failures from aggregated dashboard https://storage.googleapis.com/k8s-triage/index.html?date=2024-03-01&sig=scheduling&test=GuaranteeNonNilNodeInSchedulingCycle, do you know why @pacoxu |
Have no idea but let's leave it aside for now and see whether new failures will happen. |
Which jobs are flaking?
https://prow.k8s.io/view/gs/kubernetes-jenkins/logs/ci-kubernetes-unit/1784375152293711872
Which tests are flaking?
k8s.io/kubernetes/pkg: scheduler TestSchedulerGuaranteeNonNilNodeInSchedulingCycle
Since when has it been flaking?
04-28?
Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#ci-kubernetes-unit
Reason for failure (if possible)
Anything else we need to know?
No response
Relevant SIG(s)
/sig scheduling
The text was updated successfully, but these errors were encountered: