When CI jobs fail on the test suite, we don't see much helpful information by default: stderr: TEST: bhyvexml2argvtest ......!!.............!......!........... 40 ........................!...... 71 FAIL Some tests failed. Run them using: VIR_TEST_DEBUG=1 VIR_TEST_RANGE=7-8,22,29,65 /tmp/cirrus-ci-build/build/meson-private/dist-build/tests/bhyvexml2argvtest Following the instructions to re-run the test with VIR_TEST_DEBUG=1 is great if running locally, but quite unfriendly for CI. Signed-off-by: Daniel P. Berrangé <berrange(a)redhat.com&gt; --- Compare before: https://gitlab.com/libvirt/libvirt/-/jobs/1237988893 and after: https://gitlab.com/berrange/libvirt/-/jobs/1238324746 .gitlab-ci.yml | 2 ++ ci/cirrus/build.yml | 2 ++ 2 files changed, 4 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 35ec626113..89f618e678 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -11,6 +11,8 @@ stages: export CCACHE_DIR="$CCACHE_BASEDIR/ccache" export CCACHE_MAXSIZE="500M" export PATH="$CCACHE_WRAPPERSDIR:$PATH" + export VIR_TEST_VERBOSE="1" + export VIR_TEST_DEBUG="1" # Common templates diff --git a/ci/cirrus/build.yml b/ci/cirrus/build.yml index 2d3c46a77c..f7ef5c2d13 100644 --- a/ci/cirrus/build.yml +++ b/ci/cirrus/build.yml @@ -9,6 +9,8 @@ env: PKG_CONFIG_PATH: "@PKG_CONFIG_PATH@" PYTHON: "@PYTHON@" MAKE: "@MAKE@" + VIR_TEST_VERBOSE: "1" + VIR_TEST_DEBUG: "1" build_task: install_script: -- 2.31.1