From: Daniel P. Berrangé <berra...@redhat.com> The coverage job wants to publish a coverage report on success, but the tests might fail and in that case we need the meson logs for debugging.
Signed-off-by: Daniel P. Berrangé <berra...@redhat.com> Reviewed-by: Richard Henderson <richard.hender...@linaro.org> Message-Id: <20230623122100.1640995-3-alex.ben...@linaro.org> Message-Id: <20230503145535.91325-3-berra...@redhat.com> Signed-off-by: Alex Bennée <alex.ben...@linaro.org> --- .gitlab-ci.d/buildtest.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml index 24bba061cd..a8fd9a0c1f 100644 --- a/.gitlab-ci.d/buildtest.yml +++ b/.gitlab-ci.d/buildtest.yml @@ -462,9 +462,12 @@ gcov: coverage: /^\s*lines:\s*\d+.\d+\%/ artifacts: name: ${CI_JOB_NAME}-${CI_COMMIT_REF_NAME}-${CI_COMMIT_SHA} - when: on_success + when: always expire_in: 2 days + paths: + - build/meson-logs/testlog.txt reports: + junit: build/meson-logs/testlog.junit.xml coverage_report: coverage_format: cobertura path: build/coverage.xml -- 2.39.2