summaryrefslogtreecommitdiff
path: root/contrib/cirrus
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2021-10-26 15:13:32 -0400
committerChris Evich <cevich@redhat.com>2021-11-18 13:50:11 -0500
commit155a443a915059a2993cf3281d998e3c3a02dafb (patch)
treec0b6a09344becc699e255d1bc79f8f72fc0805bb /contrib/cirrus
parent3aa7076ff3c052e88bbee84eb2cf38f153ff89d3 (diff)
downloadpodman-155a443a915059a2993cf3281d998e3c3a02dafb.tar.gz
podman-155a443a915059a2993cf3281d998e3c3a02dafb.tar.bz2
podman-155a443a915059a2993cf3281d998e3c3a02dafb.zip
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 <cevich@redhat.com>
Diffstat (limited to 'contrib/cirrus')
-rwxr-xr-xcontrib/cirrus/runner.sh3
1 files changed, 2 insertions, 1 deletions
diff --git a/contrib/cirrus/runner.sh b/contrib/cirrus/runner.sh
index 8ef2a6e64..4c27dfa4b 100755
--- 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() {