From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Hanna Reitz" <hreitz@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
qemu-block@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Beraldo Leal" <bleal@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/2] ci: improve debuggability of I/O tests
Date: Mon, 9 May 2022 13:41:32 +0100 [thread overview]
Message-ID: <20220509124134.867431-1-berrange@redhat.com> (raw)
Currently with the TAP harness we see essentially no useful information
about the I/O tests execution. To pick a random job:
https://gitlab.com/qemu-project/qemu/-/jobs/2429330423
All that we get is this:
184/204 qemu:block / qemu-iotests qcow2 OK 309.10s 116 subtests passed
The full details are in a testlog.txt file that isn't accessible. This
series publishes that as an artifact. It further tweaks the TAP runner
to print out when it is about to run a test, so we get a record of what
was running, if the test harness gets terminated abnormally/prematurely
Daniel P. Berrangé (2):
tests/qemu-iotests: print intent to run a test in TAP mode
.gitlab-ci.d: export meson testlog.txt as an artifact
.gitlab-ci.d/buildtest-template.yml | 12 ++++++++++--
tests/qemu-iotests/testrunner.py | 3 +++
2 files changed, 13 insertions(+), 2 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-09 13:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 12:41 Daniel P. Berrangé [this message]
2022-05-09 12:41 ` [PATCH 1/2] tests/qemu-iotests: print intent to run a test in TAP mode Daniel P. Berrangé
2022-05-09 12:48 ` Thomas Huth
2022-05-09 12:41 ` [PATCH 2/2] .gitlab-ci.d: export meson testlog.txt as an artifact Daniel P. Berrangé
2022-05-09 12:51 ` Thomas Huth
2022-05-09 20:22 ` Philippe Mathieu-Daudé via
2022-05-12 10:28 ` [PATCH 0/2] ci: improve debuggability of I/O tests Kevin Wolf
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=20220509124134.867431-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=f4bug@amsat.org \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.