Re: [PULL 00/28] Misc patchesfor python, iotests, qom, crypto & io

["Daniel P. Berrangé" <berrange@redhat.com>]

On Tue, May 19, 2026 at 01:19:27PM -0400, Stefan Hajnoczi wrote:
> On Tue, May 19, 2026 at 8:52 AM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > The following changes since commit ac6721b88df944ade0048822b2b74210f543d656:
> >
> >   Merge tag 'vhost-user-rtc-pr-1' of https://gitlab.com/epilys/qemu into staging (2026-05-16 17:37:33 -0400)
> >
> > are available in the Git repository at:
> >
> >   https://gitlab.com/berrange/qemu tags/misc-next-pull-request
> >
> > for you to fetch changes up to d92ae44c28906a219e4c8e4ee8929e5fcfb2d32c:
> >
> >   qom: drop user_creatable_add_type method (2026-05-18 18:23:34 +0100)
> >
> > ----------------------------------------------------------------
> > Misc patches for python, iotests, qom, crypto & io
> >
> >  * Bump python-qemu-qmp to 0.6.0
> >  * Fix client side anoymous TLS credentials
> >  * Fix return value semantics for qio_channel_flush
> >  * Add ID validation of internal QOM constructor
> >  * Fix ability to create internal QOM objects
> >    without a parent
> >  * Merge user creatable object constructor into
> >    main QOM file
> >  * Print reason for skipping I/O tests
> >  * Remove redundant meson suits for I/O tests
> >  * Add I/O tests in meson for NBD and LUKS
> >  * Expose make targets for all block driver I/O tests
> >  * Run I/O tests for 10 block drivers in GitLab CI
> >  * Fix sudo check for LUKS I/O test
> >  * Mark I/O test 185 as flaky
> >  * Ensure stable sorting for mtest2make output
> >
> > ----------------------------------------------------------------
> 
> The following vfio_user_client tests are failed:
> https://gitlab.com/qemu-project/qemu/-/jobs/14442956771
> https://gitlab.com/qemu-project/qemu/-/jobs/14442956762
> https://gitlab.com/qemu-project/qemu/-/jobs/14442956764
> 
> Please take a look. The tests passed when I dropped your pull request
> from the staging tree, but I'm not sure what caused the failures.

Oh those are some jobs which don't run by default in forks.

Now I've manually run them I see the failures too, so I can
investigate.


With regards,
Daniel
-- 
|: https://berrange.com       ~~        https://hachyderm.io/@berrange :|
|: https://libvirt.org          ~~          https://entangle-photo.org :|
|: https://pixelfed.art/berrange   ~~    https://fstop138.berrange.com :|