ci: print stack traces on macOS if any tests fail

Mostly the tests should fail cleanly, but sometimes the test might crash
or abort. In this case we'll need to know the stack traces in order to
debug the problem. Fortunately on the Cirrus CI macOS instances, the
crash reporting service is active and saving crashes to the directory
~/Library/Logs/DiagnosticReports/

Reviewed-by: Peter Krempa <pkrempa@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

diff --git a/ci/cirrus/build.yml b/ci/cirrus/build.yml
index f03ad58143bf0cbc3c6b789ec6e8d2af616c61f1..9332e968bdc87bdb4dfe944d2b29b3807998bd23 100644 (file)
--- a/ci/cirrus/build.yml
+++ b/ci/cirrus/build.yml
@@ -26,4 +26,4 @@ build_task:
     - meson setup build
     - meson dist -C build --no-tests
     - meson compile -C build
-    - meson test -C build --no-suite syntax-check --print-errorlogs
+    - meson test -C build --no-suite syntax-check --print-errorlogs || (cat ~/Library/Logs/DiagnosticReports/*.crash && exit 1)