From: Paolo Bonzini <pbonzini@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>
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 [thread overview]
Message-ID: <f1217da2-e255-f596-1229-dc95c2388c68@redhat.com> (raw)
In-Reply-To: <b6be5064-c3aa-8666-126d-e48e47392108@redhat.com>
On 26/01/21 08:03, Thomas Huth wrote:
>>
>> + artifacts:
>> + when: always
>> + paths:
>> + - build/meson-logs/
>> + reports:
>> + junit: build/meson-logs/testlog.junit.xml
>
> Ok, I've tried that but it also worked not quite as expected:
>
> https://gitlab.com/huth/qemu/-/pipelines/246463068/test_report
>
> The "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 parent reply other threads:[~2021-01-26 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 9:03 [PATCH v1] gitlab-ci.yml: Speed up CI by using "meson test --no-rebuild" Thomas Huth
2021-01-25 9:51 ` Paolo Bonzini
2021-01-25 9:56 ` Daniel P. Berrangé
2021-01-25 10:36 ` Paolo Bonzini
2021-01-26 7:03 ` Thomas Huth
2021-01-26 8:48 ` Paolo Bonzini [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1217da2-e255-f596-1229-dc95c2388c68@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).