Cirrus: Timeout bindings test after 30m

During initial testing of Fedora 35beta VM images in CI, the bindings task was timing out. In order to allow time for collection of system details (logs), execution needs to timeout earlier than the task. Under normal conditions, the bindings test finishes in about 10-minutes. Use the ginkgo timeout option to limit execution, so it times out after 30 minutes. Also add the `-progress` option so the output more closely resembles how ginkgo runs the integration tests. Signed-off-by: Chris Evich <[email protected]>
cevich · Nov 18, 2021 · 155a443 · 155a443
1 parent 3aa7076
commit 155a443
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/contrib/cirrus/runner.sh b/contrib/cirrus/runner.sh
@@ -84,7 +84,8 @@ function _run_bindings() {
 
     # Subshell needed so logformatter will write output in cwd; if it runs in
     # the subdir, .cirrus.yml will not find the html'ized log
-    (cd pkg/bindings/test && ginkgo -trace -noColor -debug  -r) |& logformatter
+    (cd pkg/bindings/test && \
+         ginkgo -progress -trace -noColor -debug -timeout 30m -r -v) |& logformatter
 }
 
 function _run_docker-py() {