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

Move PodPriorityResolution e2e to integration #80824

Merged

Conversation

damemi
Copy link
Contributor

@damemi damemi commented Jul 31, 2019

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

NONE

/sig scheduling

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Jul 31, 2019
@damemi
Copy link
Contributor Author

damemi commented Jul 31, 2019

/cc @ravisantoshgudimetla

@k8s-ci-robot k8s-ci-robot added area/test sig/testing Categorizes an issue or PR as relevant to SIG Testing. labels Jul 31, 2019
@damemi damemi force-pushed the preemption-e2e-to-integration branch 2 times, most recently from 1c31c2e to 35a372a Compare August 1, 2019 18:16
@alculquicondor
Copy link
Member

It looks like this is flaky?

/hold

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 2, 2019
@damemi
Copy link
Contributor Author

damemi commented Aug 5, 2019

/retest

@alculquicondor
Copy link
Member

Even if the test passes after retrying, I would be opposed to merge this. We shouldn't be introducing a test that is flaky.

@damemi
Copy link
Contributor Author

damemi commented Aug 6, 2019

@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

@alculquicondor
Copy link
Member

Looking at other tests, it looks like you have to create a node before running the pod.
You should be able to run integration tests locally fairly easy. Add src/k8s.io/kubernetes/third_party/etcd to your PATH

@damemi damemi force-pushed the preemption-e2e-to-integration branch from 35a372a to a21098a Compare August 7, 2019 15:25
@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Aug 7, 2019
@damemi damemi force-pushed the preemption-e2e-to-integration branch from a21098a to 4fafd76 Compare August 7, 2019 16:07
@damemi damemi force-pushed the preemption-e2e-to-integration branch from 4fafd76 to 7830622 Compare August 26, 2019 20:17
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 26, 2019
@damemi damemi force-pushed the preemption-e2e-to-integration branch from 7830622 to 9e8b58d Compare August 26, 2019 20:21
@k8s-ci-robot k8s-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 26, 2019
Copy link
Contributor

@ravisantoshgudimetla ravisantoshgudimetla left a 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

@damemi
Copy link
Contributor Author

damemi commented Aug 29, 2019

/test pull-kubernetes-conformance-kind-ipv6

@damemi
Copy link
Contributor Author

damemi commented Aug 30, 2019

/retest

@damemi damemi force-pushed the preemption-e2e-to-integration branch from af44f08 to c6bacc7 Compare September 11, 2019 18:14
@@ -221,43 +221,6 @@ var _ = SIGDescribe("SchedulerPreemption [Serial]", func() {
})
})

var _ = SIGDescribe("PodPriorityResolution [Serial]", func() {
Copy link
Member

@Huang-Wei Huang-Wei Sep 12, 2019

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?

Copy link
Contributor Author

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)

@damemi
Copy link
Contributor Author

damemi commented Sep 12, 2019

/retest

@damemi
Copy link
Contributor Author

damemi commented Sep 18, 2019

Bumping, this is green in CI so wondering if there is any more feedback to it?

test/integration/scheduler/preemption_test.go Outdated Show resolved Hide resolved
test/e2e/scheduling/preemption.go Show resolved Hide resolved
test/integration/scheduler/preemption_test.go Outdated Show resolved Hide resolved
Namespace: metav1.NamespaceSystem,
PriorityClassName: scheduling.SystemClusterCritical,
}),
},
Copy link
Member

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?

Copy link
Contributor Author

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?

Copy link
Member

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.

Copy link
Contributor Author

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

@damemi damemi force-pushed the preemption-e2e-to-integration branch 5 times, most recently from 821a39a to 118547b Compare September 19, 2019 23:46
@damemi damemi force-pushed the preemption-e2e-to-integration branch from 118547b to ca18b48 Compare September 20, 2019 00:25
@damemi
Copy link
Contributor Author

damemi commented Sep 20, 2019

/retest

@damemi
Copy link
Contributor Author

damemi commented Sep 20, 2019

@alculquicondor updated with your feedback, please let me know if there are any other changes you'd like

@alculquicondor
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 20, 2019
@damemi
Copy link
Contributor Author

damemi commented Sep 20, 2019

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 20, 2019
Copy link
Contributor

@ravisantoshgudimetla ravisantoshgudimetla left a 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

@deads2k
Copy link
Contributor

deads2k commented Sep 20, 2019

/approve

the admission update for integration test

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 20, 2019
@k8s-ci-robot k8s-ci-robot merged commit c7619bd into kubernetes:master Sep 20, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.17 milestone Sep 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/test cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/testing Categorizes an issue or PR as relevant to SIG Testing. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants