kubebench icon indicating copy to clipboard operation
kubebench copied to clipboard

Published 20 hours ago • verified publisher icon kubeflow

"step-run" fails during long benchmark run

Open xyhuang opened this issue 6 years ago • 2 comments

This is caused by using "successCondition" in the Argo step to track the status of the created kubeflow resources (tfjob), which causes the step to timeout in a few minutes if the "successCondition" is not met. However the kubeflow resources running benchmarks might take longer time than the step can wait. We need a more proper way to track the status of the created kubeflow resources.

xyhuang avatar May 02 '18 14:05 xyhuang

/priority p2

xyhuang avatar Jun 05 '18 21:06 xyhuang

is this still an open issue and is this being handled?

Feelas avatar Jun 17 '19 10:06 Feelas