|
From: | Paolo Bonzini |
Subject: | Re: [PATCH v1] gitlab-ci.yml: Speed up CI by using "meson test --no-rebuild" |
Date: | Tue, 26 Jan 2021 09:48:07 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 |
On 26/01/21 08:03, Thomas Huth wrote:
+ artifacts: + when: always + paths: + - build/meson-logs/ + reports: + junit: build/meson-logs/testlog.junit.xmlOk, I've tried that but it also worked not quite as expected: https://gitlab.com/huth/qemu/-/pipelines/246463068/test_reportThe "check-*" jobs now show up in the test report page, but even though I've made some tests failing (e.g. the check-system-centos job), the failing jobs are showing up with "Failed: 0" there.
Hmm, that's a limitation of either TAP or GitLab. Of TAP, because it doesn't report tests when they start, so there is no test to attach the timeout to. Of GitLab, because it reports the outcome of individual testcases but not the outcome of the testsuites. Not sure how to fix it.
Also the duration is always marked with 0.00ms.
Ok, let's wait for a new Meson release before doing that too. Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |