-
Notifications
You must be signed in to change notification settings - Fork 39.4k
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
Move PodPriorityResolution e2e to integration #80824
Move PodPriorityResolution e2e to integration #80824
Conversation
1c31c2e
to
35a372a
Compare
It looks like this is flaky? /hold |
/retest |
Even if the test passes after retrying, I would be opposed to merge this. We shouldn't be introducing a test that is flaky. |
@alculquicondor yeah, I just wanted to see if I could get a better idea of the flake after retrying. Do you have any suggestions to improve it? Since this is currently an e2e test, I'm not sure where the flakiness is introduced in moving it. We would like to move some of these e2e's to integration in this manner, so if I can learn how that should be done without introducing flakes it would be very helpful |
Looking at other tests, it looks like you have to create a node before running the pod. |
35a372a
to
a21098a
Compare
a21098a
to
4fafd76
Compare
4fafd76
to
7830622
Compare
7830622
to
9e8b58d
Compare
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.
This LGTM
/cc @bsalamat
30a077a
to
af44f08
Compare
/test pull-kubernetes-conformance-kind-ipv6 |
/retest |
af44f08
to
c6bacc7
Compare
@@ -221,43 +221,6 @@ var _ = SIGDescribe("SchedulerPreemption [Serial]", func() { | |||
}) | |||
}) | |||
|
|||
var _ = SIGDescribe("PodPriorityResolution [Serial]", func() { |
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.
May I know why you want to remove this e2e test? Due to portability?
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.
The goal was to try to lower e2e load, for example in OpenShift these tests get flaky with a lot of other resources running so @ravisantoshgudimetla wanted to move as many e2e to integration as we could (with a few exceptions)
/retest |
Bumping, this is green in CI so wondering if there is any more feedback to it? |
Namespace: metav1.NamespaceSystem, | ||
PriorityClassName: scheduling.SystemClusterCritical, | ||
}), | ||
}, |
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.
Add a negative case? one for an unknown priority, and expect the scheduler to fail?
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.
Similar to my above reply, we're not setting integer values, we are setting a string and checking that it resolves to an integer, so I can't add a negative value check but I can add one for an unknown string and check that it resolves to nothing if you want. What do you think?
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.
Sorry, I didn't mean a negative number, just a negative case, i.e. a case that should be rejected.
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.
Ah, I see then I misunderstood. I added a case for an invalid priority that should be rejected
821a39a
to
118547b
Compare
118547b
to
ca18b48
Compare
/retest |
@alculquicondor updated with your feedback, please let me know if there are any other changes you'd like |
/lgtm |
/hold cancel |
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.
/approve
Thanks for the PR @damemi
/approve the admission update for integration test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: damemi, deads2k, ravisantoshgudimetla 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 |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Following #80821, this moves the e2e test checking pod priority resolution to integration to free up e2e resources
/sig scheduling