Document CI timeout and relationship with k8s jobs.
Opened this issue · 0 comments
danielkberry commented
While the CI has a timeout (5 hours?), the Argo job running on k8s will continue to run until completion or failure. This can result in users believing that their job has failed, when in reality it just took a while. Can we either extend the timeout or document the situation?