[ci][kuberay] Always cleanup KinD cluster (ray-project#27073)

wuisawesome · web-flow · commit 837ef777a32d · 2022-07-26T21:46:19.000-07:00
When cleaning up after the k8s operator tests, we should always delete the k8s cluster even if something went wrong (in fact, it's not clear we even need to clean up the resources within the cluster. 

Signed-off-by: Alex Wu &lt;itswu.alex@gmail.com&gt;
diff --git a/.buildkite/pipeline.yml b/.buildkite/pipeline.yml
@@ -426,7 +426,7 @@
     - |
       cleanup() {
         if [ "${BUILDKITE_PULL_REQUEST}" = "false" ]; then ./ci/build/upload_build_info.sh; fi
-        python python/ray/tests/kuberay/setup/teardown_kuberay.py
+        python python/ray/tests/kuberay/setup/teardown_kuberay.py || true
         kind delete cluster
       }
       trap cleanup EXIT

Original file line number	Diff line number	Diff line change
`@@ -426,7 +426,7 @@`
`426`	`426`	`- \|`
`427`	`427`	`cleanup() {`
`428`	`428`	`if [ "${BUILDKITE_PULL_REQUEST}" = "false" ]; then ./ci/build/upload_build_info.sh; fi`
`429`		`- python python/ray/tests/kuberay/setup/teardown_kuberay.py`
	`429`	`+ python python/ray/tests/kuberay/setup/teardown_kuberay.py \|\| true`
`430`	`430`	`kind delete cluster`
`431`	`431`	`}`
`432`	`432`	`trap cleanup EXIT`