Daniel P. Berrangé wrote:
> On Mon, Feb 02, 2026 at 09:02:29PM +0100, Roman Bogorodskiy wrote:
> > Daniel P. Berrangé wrote:
> >
> > > On Mon, Feb 02, 2026 at 08:39:32PM +0100, Peter Krempa via Devel wrote:
> > > > On Mon, Feb 02, 2026 at 20:27:36 +0100, Roman Bogorodskiy wrote:
> > > > > Michal Prívozník wrote:
> > > >
> > > > [...]
> > > >
> > > > > Looks like this broke aarch64-macos-14.
> > > > >
> > > > > I think it also needs this:
> > > > >
> > > > > --- a/meson.build
> > > > > +++ b/meson.build
> > > > > @@ -896,6 +896,7 @@ endif
> > > > >
> > > > > if xdr_dep.found()
> > > > > xdrproc_3arg_code = '''
> > > > > + #include <rpc/types.h>
> > > > > #include <rpc/xdr.h>
> > > > >
> > > > > bool_t test_filter(XDR *xdr, void *data, unsigned int
> > > > > opaque_flags) {
> > > > >
> > > > > I wonder though if it's possible to somehow trigger aarch64-macos-14
> > > > > on
> > > > > feature branches because I don't seem to see that in my pipelines.
> > > >
> > > > You should be able to setup cirrus for yourself. The steps I've followed
> > > > the rather long time ago I've set it up are documented in ci/README.rst
> > > >
> > > > You then push into your clone with:
> > > >
> > > > git push -o ci.variable=RUN_PIPELINE_UPSTREAM_ENV=1
> > >
> > > Just RUN_PIPELINE=1 generally - RUN_PIPELINE_UPSTREAM_ENV=1 uses cached
> > > upstream containers that might not match your branch requirements.
> > >
> > > With regards,
> > > Daniel
> >
> > Yeah, that's what I've been using for quite some time as well for
> > pre-review / pre-push checks.
> >
> > E.g. for this specific push I used:
> >
> > https://gitlab.com/rbogorodskiy/libvirt/-/pipelines/2301366479
> >
> > The thing is that the job list does not include aarch64-macos-14.
>
> Right, the limitation we have is that we can only provide out-of-the-box
> CI for jobs hosted on gitlab.
>
> The FreeBSD and macOS jobs are both hosted on Cirrus CI, with gitlab
> just being a facade, via 'cirrus-run'. It extra hacky as it also
> involves a dummy github repo
>
> There are instructions for setting up Cirrus CI in ci/README.rst
>
> Once that's setup, then cirrus CI jobs get enabled in the pipeline
I got it working, thanks!
> 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 :|
>
