-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Check status of framework.CheckPodsRunningReady #25915
Conversation
Failing fast always better than failing slow, LGTM. |
There are several dubious calls of |
Change LGTM. Thanks! @ncdc, if you're willing to clean up the rest of the calls in the file, that'd be even better. |
I can do it in a bit On Thursday, May 19, 2016, Yu-Ju Hong notifications@github.com wrote:
|
That's great! |
@yujuhong I think I got the rest of them; PTAL |
Thanks! |
This PR should help with debugging flakes. Marking it p2 for now. |
@ncdc Please rebase! |
Will do shortly On Friday, May 20, 2016, Mike Danese notifications@github.com wrote:
|
Check status of framework.CheckPodsRunningReady and fail test if it's false, instead of silently ignoring the failure.
@mikedanese @yujuhong rebased |
Thanks! |
GCE e2e build/test passed for commit f83a286. |
Automatic merge from submit-queue |
Automatic merge from submit-queue support Azure data disk volume This is a WIP of supporting azure data disk volume. Will add test and dynamic provisioning support once #29006 is merged replace #25915 fix #23259 @kubernetes/sig-storage @colemickens @brendandburns
Check status of framework.CheckPodsRunningReady and fail test if it's false, instead of silently
ignoring the failure.
This doesn't fix whatever is causing the pod not to start in #17523 but it does fail the test as soon as it detects the pod didn't start, instead of allowing the testing to proceed.
cc @kubernetes/sig-testing @spxtr @ixdy @kubernetes/rh-cluster-infra