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
Update and improve Endpoints resource lifecycle test #92891
Update and improve Endpoints resource lifecycle test #92891
Conversation
/release-note-none |
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 feel like this is about halfway toward where I was suggesting we take this
test/e2e/network/service.go
Outdated
break | ||
} | ||
} | ||
framework.ExpectEqual(eventFound, true, "failed to find Endpoints %v event", watch.Deleted) |
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.
So we're verifying that a deleted event has occurred. Is this the same thing as verifying that the Endpoints object has been deleted? I would suggest trying to retrieve the Endpoints to verify it's no longer there as demonstrated in 225e7c7#diff-cfb4fba63c5d60607f76e0c2e1266d77R225-R231
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.
Updated in 95e41663d7ef330874fad713e664b11e1ca320cb
test/e2e/network/service.go
Outdated
|
||
// set up a watch for the Endpoint | ||
// this timeout was chosen as there was timeout failure from the CI | ||
endpointWatchTimeoutSeconds := int64(180) | ||
endpointWatch, err := f.ClientSet.CoreV1().Endpoints(ns).Watch(context.TODO(), metav1.ListOptions{LabelSelector: "testendpoint-static=true", TimeoutSeconds: &endpointWatchTimeoutSeconds}) | ||
endpointWatch, err := f.ClientSet.CoreV1().Endpoints(testNamespaceName).Watch(context.TODO(), metav1.ListOptions{LabelSelector: "test-endpoint-static=true", TimeoutSeconds: &endpointWatchTimeoutSeconds}) |
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.
Using a bare watch like this is susceptible to disconnects. Please consider using k8s.io/client-go/tools/watch.Until as demonstrated in 4582e26 instead of a for event := range chan
loop
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.
Updated in e65a1cc661e104a61ef5abe1feac1cbdbc94f100
/test pull-kubernetes-e2e-gce-device-plugin-gpu |
/test pull-kubernetes-integration |
/test pull-kubernetes-e2e-gce-device-plugin-gpu |
/test pull-kubernetes-kubemark-e2e-gce-big |
/test pull-kubernetes-e2e-gce-device-plugin-gpu |
/retest |
1 similar comment
/retest |
849ee94
to
b0b4ca7
Compare
/retest |
1 similar comment
/retest |
b0b4ca7
to
93c0f19
Compare
/retest |
3 similar comments
/retest |
/retest |
/retest |
@Riaankl 👋 Can you please squash the commits into a single commit? Looks ready to go otherwise! |
@spiffxp @Riaankl Also, does this need to be in the 1.19 milestone? Given that master will be open for 1.20 soon, only blocker bugs are being considered for 1.19. |
Hi Nikhita! Test Freeze is Thu, August 6. My understanding is that if we merge this week (today?), we would have the required two weeks flake free we need for this test to be further modified for the 1.19 release. Thank you for your help and leadership in the community! |
948c102
to
c9acca7
Compare
Ah yes, you are right! I came across this while trying to wrangle the PRs
with 1.19 milestone. Sorry for the noise! :)
…On Thu, 23 Jul, 2020, 12:45 AM Hippie Hacker, ***@***.***> wrote:
Hi Nikhita!
Test Freeze is Thu, August 6. My understanding is that if we merge this
week (today?), we would have the required two weeks flake free we need for
this test to be further modified for the 1.19 release.
-
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/conformance-tests.md#promoting-tests-to-conformance
Thank you for your help and leadership in the community!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#92891 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUGYSY3V3VATSJKXZJLR443GLANCNFSM4OT5RL5A>
.
|
@nikhita Thank you for your support. @BobyMCbobs squashed the commits. |
/test pull-kubernetes-e2e-kind |
/test pull-kubernetes-kubemark-e2e-gce-big |
/test pull-kubernetes-e2e-gce |
@spiffxp already approved, and I've looked through this and feel that @BobyMCbobs addressed @spiffxp comments. |
/test pull-kubernetes-e2e-gce-100-performance |
/retest |
1 similar comment
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Improves naming, adds more checks throughout the test:
Which issue(s) this PR fixes:
Fixes #90923
Special notes for your reviewer:
Relate to PR #90939 improvement
Does this PR introduce a user-facing change?:
Release note:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
/sig testing
/sig architecture
/area conformance