-
Notifications
You must be signed in to change notification settings - Fork 39k
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] ci-kubernetes-unit (error message's order sensitivity) #125221
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-sigs/prow repository. |
/remove-sig testing This appears to be a flake in scheduler unit tests which would be sig scheduling ( kubernetes/pkg/scheduler/OWNERS Line 4 in b503409
|
.. and it appears to be DRA specific subset of scheduling so |
FYI - looks like this is happening every 3-6 hours give or take. Yesterday it was every six hours and today it seems to be every 3-4 hours. Looking into it a bit more, it looks like it may just be an issue with a connection via the test while it's trying to hit the server. I don't think the test itself is failing, I think the connection to the server is failing. CC @Vyom-Yadav |
Hey All - hope you're well. Michael here from the Release Signal team. Just wanted to touch base and make sure we're good to go for the cut on the 4th. CC @BenTheElder |
Which jobs are flaking?
master-blocking:
Which tests are flaking?
k8s.io/kubernetes/pkg/scheduler/framework/plugins/dynamicresources.dynamicresources
Since when has it been flaking?
It starts flaking today 30-05-2024
Testgrid link
https://testgrid.k8s.io/sig-release-master-blocking#ci-kubernetes-unit
Reason for failure (if possible)
The test fail is
TestPlugin/too-many-translated-claim-parameters/prefilter
This failure may be caused by the error message's order sensitivity.
The error message's order of Resource Classes
[default/my-resource-class default/other]
versus[default/other default/my-resource-class]
is different.Anything else we need to know?
N/A
Relevant SIG(s)
/sig node
/sig scheduling
@kubernetes/release-team-release-signal
The text was updated successfully, but these errors were encountered: