From e5634027010a08afc919e1e1c9e74db3f232757f Mon Sep 17 00:00:00 2001 From: Aaron Crickenberger Date: Mon, 25 Feb 2019 07:34:46 -0800 Subject: [PATCH] Fix test-cmd kubectl_run flake It is unrealistic to expect a cascading delete to immediately take effect. Somehow this test got away with it for a while, but we have finally reached a point where apiserver performance has changed just enough to expsoe this flaky expectation. --- test/cmd/run.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/cmd/run.sh b/test/cmd/run.sh index 38d03854b6..ae877af323 100755 --- a/test/cmd/run.sh +++ b/test/cmd/run.sh @@ -36,7 +36,7 @@ run_kubectl_run_tests() { # Clean up kubectl delete jobs pi "${kube_flags[@]}" # Post-condition: no pods exist. - kube::test::get_object_assert pods "{{range.items}}{{$id_field}}:{{end}}" '' + kube::test::wait_object_assert pods "{{range.items}}{{$id_field}}:{{end}}" '' # Pre-Condition: no Deployment exists kube::test::get_object_assert deployment "{{range.items}}{{$id_field}}:{{end}}" ''