From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Hanna Reitz" <hreitz@redhat.com>,
"Kevin Wolf" <kwolf@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [PATCH RFC/WIP 4/4] gitlab: add jobs for thorough block tests
Date: Wed, 8 Oct 2025 17:23:10 +0100 [thread overview]
Message-ID: <aOaP7sBjIMRpCOgu@redhat.com> (raw)
In-Reply-To: <wboov2wdkicvhzwpkckoav3d4uwghdzd7g6kwzy3ynrdt3cyr4@qeu6nviffl2i>
On Wed, Oct 08, 2025 at 10:57:45AM -0500, Eric Blake wrote:
> On Wed, Oct 08, 2025 at 12:35:52PM +0100, Daniel P. Berrangé wrote:
> > CI is only exercising the qcow2 'auto' tests currently. As a result we
> > get no exposure of changes which cause regressions in other block format
> > drivers.
> >
> > This adds new CI jobs for each block format, that will run the target
> > 'make check-block-$FORMAT'. The jobs are separate so that we have the
> > ability to make each formats gating or not, depending on their level
> > of reliability.
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > .gitlab-ci.d/buildtest.yml | 63 ++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 63 insertions(+)
>
> The idea makes sense to me.
>
> Did you have a link a URL of a CI run that failed tests on NBD, where
> I might be able to help make the tests more deterministic?
Its the one in the cover letter - the nbd job is
https://gitlab.com/berrange/qemu/-/jobs/11633680715
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-10-08 16:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 11:35 [PATCH 0/4] tests: do more testing of block drivers in CI Daniel P. Berrangé
2025-10-08 11:35 ` [PATCH 1/4] tests: print reason when I/O test is skipped in TAP mode Daniel P. Berrangé
2025-10-08 11:47 ` Thomas Huth
2025-10-08 11:35 ` [PATCH 2/4] tests: rearrange suites for I/O tests Daniel P. Berrangé
2025-10-14 8:26 ` Kevin Wolf
2025-10-15 13:44 ` Daniel P. Berrangé
2025-10-15 13:47 ` Thomas Huth
2025-10-15 13:48 ` Daniel P. Berrangé
2025-10-08 11:35 ` [PATCH 3/4] tests: add nbd and luks to the I/O test suites Daniel P. Berrangé
2025-10-08 11:55 ` Thomas Huth
2025-10-08 12:55 ` Daniel P. Berrangé
2025-10-08 13:03 ` Thomas Huth
2025-10-08 15:55 ` Eric Blake
2025-10-14 8:50 ` Kevin Wolf
2025-10-14 20:19 ` Eric Blake
2025-10-08 15:49 ` Eric Blake
2025-10-08 11:35 ` [PATCH RFC/WIP 4/4] gitlab: add jobs for thorough block tests Daniel P. Berrangé
2025-10-08 15:57 ` Eric Blake
2025-10-08 16:23 ` Daniel P. Berrangé [this message]
2025-10-13 21:46 ` Eric Blake
2025-10-10 11:55 ` Thomas Huth
2025-10-10 12:11 ` Daniel P. Berrangé
2025-10-08 16:28 ` [PATCH 0/4] tests: do more testing of block drivers in CI Daniel P. Berrangé
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=aOaP7sBjIMRpCOgu@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=eblake@redhat.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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).