From: Cleber Rosa <crosa@redhat.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Willian Rampazzo" <wrampazz@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: [PATCH 3/3] Acceptance tests: show test report on GitLab CI
Date: Mon, 12 Oct 2020 17:18:49 -0400 [thread overview]
Message-ID: <20201012211849.GA960048@localhost.localdomain> (raw)
In-Reply-To: <87tuuzzj3x.fsf@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]
On Mon, Oct 12, 2020 at 02:09:22PM +0100, Alex Bennée wrote:
>
> Philippe Mathieu-Daudé <philmd@redhat.com> writes:
>
> > On 10/9/20 10:55 PM, Cleber Rosa wrote:
> >> Avocado will, by default, produce JUnit files. Let's ask GitLab
> >> to present those in the web UI.
> >
> > https://gitlab.com/philmd/qemu/-/pipelines/200764992/test_report
> >
> > Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> > Tested-by: Philippe Mathieu-Daudé <philmd@redhat.com>
>
> That's awesome - I wonder if the tap reports can also be read?
>
Not according to:
https://docs.gitlab.com/ee/ci/pipelines/job_artifacts.html#artifactsreports
But, I'm working on further integrating Avocado to other types of
tests in QEMU, so users can choose to run test jobs with any
combination of test types.
A very rough PoC with some unit tests (that generate TAP) being run
by Avocado, and the JUnit report being displayed, can be seen here:
https://gitlab.com/cleber.gnu/qemu/-/pipelines/201609047/test_report
The grand vision is, among other things, to be able run tests related
to a given subsystem or feature, say "migration", no matter what type
of tests they are.
Cheers,
- Cleber.
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
>
> --
> Alex Bennée
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-12 21:19 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 20:55 [PATCH 0/3] Acceptance Tests: improve usage on GitLab CI Cleber Rosa
2020-10-09 20:55 ` [PATCH 1/3] Acceptance tests: bump pycdlib version for easier installation Cleber Rosa
2020-10-10 7:36 ` Philippe Mathieu-Daudé
2020-10-10 7:36 ` [Bug 1897783] " Philippe Mathieu-Daudé
2020-10-12 1:16 ` Cleber Rosa
2020-10-19 16:02 ` Willian Rampazzo
2020-10-19 16:02 ` [Bug 1897783] " Willian Rampazzo
2020-10-09 20:55 ` [PATCH 2/3] Acceptance tests: do not show canceled test logs on GitLab CI Cleber Rosa
2020-10-10 9:10 ` Philippe Mathieu-Daudé
2020-10-09 20:55 ` [PATCH 3/3] Acceptance tests: show test report " Cleber Rosa
2020-10-10 9:11 ` Philippe Mathieu-Daudé
2020-10-12 13:09 ` Alex Bennée
2020-10-12 21:18 ` Cleber Rosa [this message]
2020-10-12 10:32 ` [PATCH 0/3] Acceptance Tests: improve usage " Thomas Huth
-- strict thread matches above, loose matches on Subject: below --
2020-09-29 18:09 [Bug 1897783] [NEW] avocado tests not running on aarch64 host Philippe Mathieu-Daudé
2020-09-29 19:27 ` [Bug 1897783] " Philippe Mathieu-Daudé
2020-09-29 20:37 ` Cleber Rosa
2020-09-29 20:46 ` Cleber Rosa
2020-09-29 20:52 ` Cleber Rosa
2020-10-09 21:01 ` Cleber Rosa
2020-12-10 9:05 ` Thomas Huth
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=20201012211849.GA960048@localhost.localdomain \
--to=crosa@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=ehabkost@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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).