Skip to content
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

Closed
wendy-ha18 opened this issue May 30, 2024 · 5 comments · Fixed by #125213
Closed

[Flaking Test] ci-kubernetes-unit (error message's order sensitivity) #125221

wendy-ha18 opened this issue May 30, 2024 · 5 comments · Fixed by #125213
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@wendy-ha18
Copy link
Member

wendy-ha18 commented May 30, 2024

Which jobs are flaking?

master-blocking:

  • ci-kubernetes-unit

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.

{Failed;Failed;Failed;  === RUN   TestPlugin/too-many-translated-class-parameters/prefilter
    dynamicresources_test.go:1103: 
        	Error Trace:	/home/prow/go/src/k8s.io/kubernetes/pkg/scheduler/framework/plugins/dynamicresources/dynamicresources_test.go:1221
        	            				/home/prow/go/src/k8s.io/kubernetes/pkg/scheduler/framework/plugins/dynamicresources/dynamicresources_test.go:1103
        	Error:      	Not equal: 
        	            	expected: &framework.Status{code:1, reasons:[]string(nil), err:(*errors.errorString)(0xc00053d6b0), plugin:""}
        	            	actual  : &framework.Status{code:1, reasons:[]string(nil), err:(*errors.errorString)(0xc000b7b7f0), plugin:""}
        	            	
        	            	Diff:
        	            	--- Expected
        	            	+++ Actual
        	            	@@ -4,3 +4,3 @@
        	            	  err: (*errors.errorString)({
        	            	-  s: (string) (len=142) "multiple generated class parameters for ResourceClassParameters.example.com my-resource-class found: [default/my-resource-class default/other]"
        	            	+  s: (string) (len=142) "multiple generated class parameters for ResourceClassParameters.example.com my-resource-class found: [default/other default/my-resource-class]"
        	            	  }),
        	Test:       	TestPlugin/too-many-translated-class-parameters/prefilter
        --- FAIL: TestPlugin/too-many-translated-class-parameters/prefilter (0.00s)

Anything else we need to know?

N/A

Relevant SIG(s)

/sig node
/sig scheduling
@kubernetes/release-team-release-signal

@wendy-ha18 wendy-ha18 added the kind/flake Categorizes issue or PR as related to a flaky test. label May 30, 2024
@k8s-ci-robot k8s-ci-robot added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label May 30, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 30, 2024
@BenTheElder BenTheElder changed the title [Flaking Test][sig-testing] ci-kubernetes-unit (error message's order sensitivity) [Flaking Test] ci-kubernetes-unit (error message's order sensitivity) May 30, 2024
@BenTheElder
Copy link
Member

/remove-sig testing
/sig scheduling
(sig testing doesn't own all of the unit tests, just test frameworks, tooling, CI infra, etc)

This appears to be a flake in scheduler unit tests which would be sig scheduling (

- sig-scheduling-maintainers
)

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels May 30, 2024
@BenTheElder
Copy link
Member

.. and it appears to be DRA specific subset of scheduling so
/sig node
as well

@k8s-ci-robot k8s-ci-robot added the sig/node Categorizes an issue or PR as relevant to SIG Node. label May 30, 2024
@AdminTurnedDevOps
Copy link

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.

Image

CC @Vyom-Yadav

@AdminTurnedDevOps
Copy link

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
/sig-node

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/node Categorizes an issue or PR as relevant to SIG Node. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
Development

Successfully merging a pull request may close this issue.

4 participants