-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
e2e test cases should clean up more effectively #12408
e2e test cases should clean up more effectively #12408
Conversation
GCE e2e build/test passed for commit 9e3c742ded50f7f247a9b1f1783e3c85cbf69971. |
Ping - trying to get this cleared so we can get graceful deletion unblocked |
|
||
pods, err = podClient.List(labels.SelectorFromSet(labels.Set(map[string]string{"time": value})), fields.Everything()) | ||
if err != nil { | ||
Fail(fmt.Sprintf("Failed to delete pod: %v", err)) |
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 is more "failed to list" than "failed to delete", right?
9e3c742
to
479ba5c
Compare
Addressed feedback |
GCE e2e build/test passed for commit 479ba5cd7a62d7c3b9c8582f26127766ac24837b. |
other than those two issues, LGTM |
479ba5c
to
e623d33
Compare
Graceful deletion exposes weakness in cleanup paths, add common hooks for waiting for namespcae deletion to complete, use direct delection where necessary, and add some debug output for finding cleanup flags (namespaces that aren't fully deleted)
GCE e2e build/test passed for commit e623d33. |
Comments addressed |
LGTM, thanks! |
e2e test cases should clean up more effectively
Graceful deletion exposes weakness in cleanup paths, add
common hooks for waiting for namespace deletion to complete,
use direct delection where necessary, and add some debug output
for finding cleanup flags (namespaces that aren't fully deleted)
Extracted from #9165 - makes e2e more resilient to transients