-
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
code cleanup for pkg/scheduler #100947
code cleanup for pkg/scheduler #100947
Conversation
@lojies: 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. |
Hi @lojies. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
@@ -181,8 +181,7 @@ func (pl *SelectorSpread) PreScore(ctx context.Context, cycleState *framework.Cy | |||
if skipSelectorSpread(pod) { | |||
return nil | |||
} | |||
var selector labels.Selector | |||
selector = helper.DefaultSelector( | |||
var selector = helper.DefaultSelector( |
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.
var selector = helper.DefaultSelector( | |
selector := helper.DefaultSelector( |
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.
+1
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.
Thanks for the suggestion, i have changed this.
@@ -29,7 +29,6 @@ import ( | |||
|
|||
"k8s.io/api/core/v1" | |||
metav1 "k8s.io/apimachinery/pkg/apis/meta/v1" | |||
"k8s.io/apimachinery/pkg/types" | |||
ktypes "k8s.io/apimachinery/pkg/types" |
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.
Would it be better to use "k8s.io/apimachinery/pkg/types"
instead of ktypes "k8s.io/apimachinery/pkg/types"
?
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.
Yup. Seems other places are all using "k8s.io/apimachinery/pkg/types" directly, and only scheduler code are using the "ktypes" alias:
pkg/scheduler/internal/queue/scheduling_queue.go
34: ktypes "k8s.io/apimachinery/pkg/types"
pkg/scheduler/internal/queue/scheduling_queue_test.go
31: ktypes "k8s.io/apimachinery/pkg/types"
9b44e76
to
953cd15
Compare
/retest |
1 similar comment
/retest |
/test pull-kubernetes-e2e-gce-ubuntu-containerd |
/lgtm Thanks! |
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.
One final nit. Would you mind removing the ktypes
alias in pkg/scheduler/internal/queue/scheduling_queue.go?
953cd15
to
5ddb1be
Compare
@Huang-Wei , i have removed |
/lgtm Thanks! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Huang-Wei, lojies 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 |
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
https://staticcheck.io/docs/checks
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: