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
Scheduler: organize framework unit tests in subtests #98588
Conversation
@gavinfish: 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. |
/assign @Huang-Wei |
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 @gavinfish !
statusMap: PluginToStatus{"p1": NewStatus(Success), "p2": NewStatus(UnschedulableAndUnresolvable), "p3": NewStatus(Unschedulable)}, | ||
wantCode: UnschedulableAndUnresolvable, | ||
}, | ||
{ | ||
name: "merge nil status", | ||
wantCode: Success, | ||
}, | ||
} | ||
|
||
for i, test := range tests { |
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.
Let's remove the i
and test $i
below (L131)
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.
All unnecessary test scenario information in error has been removed.
@@ -401,7 +401,7 @@ func TestEnoughRequests(t *testing.T) { | |||
for _, test := range enoughPodsTests { | |||
t.Run(test.name, func(t *testing.T) { | |||
node := v1.Node{Status: v1.NodeStatus{Capacity: makeResources(10, 20, 32, 5, 20, 5).Capacity, Allocatable: makeAllocatableResources(10, 20, 32, 5, 20, 5)}} | |||
test.nodeInfo.SetNode(&node) | |||
_ = test.nodeInfo.SetNode(&node) |
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.
Is this necessary?
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.
No, the point here is that this func may return an error somethings, but we know it will not in this test or we can safely ignore it.
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.
I don't think it's a common pattern used in Go projects. Correct me if I'm wrong. Otherwise, let's keep the original logic.
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.
reverted
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.
Just FYI, get Do not discard errors using _ variables.
when going through https://github.com/golang/go/wiki/CodeReviewComments#handle-errors.
76db936
to
0b55017
Compare
/test pull-kubernetes-e2e-gce-ubuntu-containerd |
0b55017
to
0c3d8b9
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gavinfish, Huang-Wei 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 |
/test pull-kubernetes-e2e-kind-ipv6 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Organize unit tests in subtests.
Which issue(s) this PR fixes:
Xref #98573
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: