ci: integration: Only create a coredump log when a core exists

It could be quite confusing looking at the job log artifacts and having
an empty coredump log in there, IOW it doesn't really give much
confidence that the reporting mechanism actually works.

Signed-off-by: Erik Skultety <eskultet@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>

diff --git a/ci/integration-template.yml b/ci/integration-template.yml
index 2e7802dbe045f481ac9877c039a795d9fedc5993..4321f0d29e1698815316ca544e18f3db1ff8f416 100644 (file)
--- a/ci/integration-template.yml
+++ b/ci/integration-template.yml
@@ -57,7 +57,7 @@
 .collect-logs: &collect-logs
   - mkdir logs
   - test -d "$SCRATCH_DIR"/avocado && sudo mv "$SCRATCH_DIR"/avocado/latest/test-results logs/avocado;
-  - sudo coredumpctl info --no-pager > logs/coredumpctl.txt
+  - sudo coredumpctl &>/dev/null && sudo coredumpctl info --no-pager > logs/coredumpctl.txt
   - sudo mv /var/log/libvirt logs/libvirt
   - sudo chown -R $(whoami):$(whoami) logs
     # rename all Avocado stderr/stdout logs to *.log so that GitLab's web UI doesn't mangle the MIME type