[Flaking Test] [sig-scheduling] TestSchedulerSchedulePod

[pacoxu]

Which jobs are flaking?

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/122027/pull-kubernetes-unit/1735186633038237696

Which tests are flaking?

k8s.io/kubernetes/pkg: scheduler

{Failed;Failed;  === RUN   TestSchedulerSchedulePod/test_no_score_plugin,_prefilter_plugin_returning_2_nodes,_only_1_node_is_evaluated
    node_tree.go:65: I1214 06:59:28.565440] Added node in listed group to NodeTree node="node1" zone=""
    node_tree.go:65: I1214 06:59:28.565571] Added node in listed group to NodeTree node="node2" zone=""
    node_tree.go:65: I1214 06:59:28.565780] Added node in listed group to NodeTree node="node3" zone=""
W1214 06:59:28.565971   50310 mutation_detector.go:53] Mutation detector is enabled, this will result in memory leakage.
    framework.go:368: I1214 06:59:28.566481] the scheduler starts to work with those plugins Plugins={"PreEnqueue":{"Enabled":null,"Disabled":null},"QueueSort":{"Enabled":[{"Name":"PrioritySort","Weight":0}],"Disabled":null},"PreFilter":{"Enabled":[{"Name":"FakePreFilter","Weight":0}],"Disabled":null},"Filter":{"Enabled":null,"Disabled":null},"PostFilter":{"Enabled":null,"Disabled":null},"PreScore":{"Enabled":null,"Disabled":null},"Score":{"Enabled":null,"Disabled":null},"Reserve":{"Enabled":null,"Disabled":null},"Permit":{"Enabled":null,"Disabled":null},"PreBind":{"Enabled":null,"Disabled":null},"Bind":{"Enabled":[{"Name":"DefaultBinder","Weight":0}],"Disabled":null},"PostBind":{"Enabled":null,"Disabled":null},"MultiPoint":{"Enabled":null,"Disabled":null}}
    schedule_one_test.go:2437: Expected: map[node1:{} node3:{}], got: node2
    --- FAIL: TestSchedulerSchedulePod/test_no_score_plugin,_prefilter_plugin_returning_2_nodes,_only_1_node_is_evaluated (0.10s)
;=== RUN   TestSchedulerSchedulePod
--- FAIL: TestSchedulerSchedulePod (2.78s)
;}

Since when has it been flaking?

today after #122022 is merged. Edited

caused by #122058

Testgrid link

NA

Reason for failure (if possible)

N/A

Anything else we need to know?

/cc @sanposhiho

Relevant SIG(s)

/sig scheduling

[k8s-ci-robot]

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/test-infra repository.

[AxeZhan]

/cc

[sanposhiho]

I believe, after merging #122058 is more correct.
The flaky test is introduced by that PR.

[sanposhiho]

cc @aleksandra-malinowska

[pacoxu]

I believe, after merging #122058 is more correct. The flaky test is introduced by that PR.

Thanks for correcting me. I updated the issue description.

[pacoxu]

https://prow.k8s.io/job-history/gs/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-unit

• failed 4 in last ~20 runs, a very high flake rate.

I would suggest reverting it or fixing it ASAP.