On Fri, Jan 16, 2026 at 08:53:53AM +0100, Thomas Huth wrote: > On 15/01/2026 17.47, 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 format gating or not, depending on their level > > of reliability. > > > > There is currently an undiagnosed failure of job 185 with the qcow2 when > > run in CI that is marked to be skipped, reported at: > > > > https://gitlab.com/qemu-project/qemu/-/issues/3270 > > > > Signed-off-by: Daniel P. Berrangé <[email protected]> > > --- > > .gitlab-ci.d/buildtest.yml | 92 ++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 92 insertions(+) > > > > diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml > > index dfe954fe3c..91b398bd63 100644 > > --- a/.gitlab-ci.d/buildtest.yml > > +++ b/.gitlab-ci.d/buildtest.yml > > @@ -176,6 +176,98 @@ build-system-centos: > > x86_64-softmmu rx-softmmu sh4-softmmu > > MAKE_CHECK_ARGS: check-build > > Reviewed-by: Thomas Huth <[email protected]> > > One more though: I think we could then also remove the iotests from the > "build-tcg-disabled" job since they should now be covered by this new job... > WDYT?
Oh, I never noticed we had randomly stuffed a bunch of extra iotests into that job ! That is redundant *provided* we can indeed go forward with the new block-raw & block-qcow2 jobs being gating jobs. 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 :|
