mirror of
https://github.com/k3s-io/kubernetes.git
synced 2025-07-23 19:56:01 +00:00
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.
This commit is contained in:
parent
1eb2acca99
commit
e563402701
@ -36,7 +36,7 @@ run_kubectl_run_tests() {
|
|||||||
# Clean up
|
# Clean up
|
||||||
kubectl delete jobs pi "${kube_flags[@]}"
|
kubectl delete jobs pi "${kube_flags[@]}"
|
||||||
# Post-condition: no pods exist.
|
# 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
|
# Pre-Condition: no Deployment exists
|
||||||
kube::test::get_object_assert deployment "{{range.items}}{{$id_field}}:{{end}}" ''
|
kube::test::get_object_assert deployment "{{range.items}}{{$id_field}}:{{end}}" ''
|
||||||
|
Loading…
Reference in New Issue
Block a user