This is a collection of fixes required to get CI back to green.
Given that 2 of 3 apply to cirrus, I had to push them to staging to
even try them.  Since it worked, I've now pushed them to master.


r~


Richard Henderson (1):
  gitlab-ci/cirrus: Update freebsd to python 3.9 packages

Vladimir Sementsov-Ogievskiy (2):
  iotests: fix copy-before-write for macOS and FreeBSD
  iotests/copy-before-write: specify required_fmts

 .gitlab-ci.d/cirrus/freebsd-12.vars        | 3 ++-
 .gitlab-ci.d/cirrus/freebsd-13.vars        | 3 ++-
 tests/qemu-iotests/tests/copy-before-write | 8 +++++++-
 3 files changed, 11 insertions(+), 3 deletions(-)

-- 
2.34.1

On Tue, Jul 12, 2022 at 03:28:58PM +0530, Richard Henderson wrote:
> This is a collection of fixes required to get CI back to green.
> Given that 2 of 3 apply to cirrus, I had to push them to staging to
> even try them.  Since it worked, I've now pushed them to master.

FWIW, it is possible to test Cirrus CI fixes in your own personal
fork too, but it needs a little extra setup first, detailed in

  .gitlab-ci.d/cirrus/README.rst

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 :|

On 7/12/22 15:43, Daniel P. Berrangé wrote:
> On Tue, Jul 12, 2022 at 03:28:58PM +0530, Richard Henderson wrote:
>> This is a collection of fixes required to get CI back to green.
>> Given that 2 of 3 apply to cirrus, I had to push them to staging to
>> even try them.  Since it worked, I've now pushed them to master.
> 
> FWIW, it is possible to test Cirrus CI fixes in your own personal
> fork too, but it needs a little extra setup first, detailed in
> 
>    .gitlab-ci.d/cirrus/README.rst

How many of the 'github' strings therein should really be 'gitlab'?


r~

On Tue, Jul 12, 2022 at 03:56:54PM +0530, Richard Henderson wrote:
> On 7/12/22 15:43, Daniel P. Berrangé wrote:
> > On Tue, Jul 12, 2022 at 03:28:58PM +0530, Richard Henderson wrote:
> > > This is a collection of fixes required to get CI back to green.
> > > Given that 2 of 3 apply to cirrus, I had to push them to staging to
> > > even try them.  Since it worked, I've now pushed them to master.
> > 
> > FWIW, it is possible to test Cirrus CI fixes in your own personal
> > fork too, but it needs a little extra setup first, detailed in
> > 
> >    .gitlab-ci.d/cirrus/README.rst
> 
> How many of the 'github' strings therein should really be 'gitlab'?

None actually, this is all part of the (gross) hack. Cirrus CI officially
only integrates with GitHub, so we need a dummy GitHub repo there. Once
the job starts though, it actually pulls the real code from gitlab.

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 :|

On Tue, Jul 12, 2022 at 4:33 AM Daniel P. Berrangé <berrange@redhat.com>
wrote:

> On Tue, Jul 12, 2022 at 03:56:54PM +0530, Richard Henderson wrote:
> > On 7/12/22 15:43, Daniel P. Berrangé wrote:
> > > On Tue, Jul 12, 2022 at 03:28:58PM +0530, Richard Henderson wrote:
> > > > This is a collection of fixes required to get CI back to green.
> > > > Given that 2 of 3 apply to cirrus, I had to push them to staging to
> > > > even try them.  Since it worked, I've now pushed them to master.
> > >
> > > FWIW, it is possible to test Cirrus CI fixes in your own personal
> > > fork too, but it needs a little extra setup first, detailed in
> > >
> > >    .gitlab-ci.d/cirrus/README.rst
> >
> > How many of the 'github' strings therein should really be 'gitlab'?
>
> None actually, this is all part of the (gross) hack. Cirrus CI officially
> only integrates with GitHub, so we need a dummy GitHub repo there. Once
> the job starts though, it actually pulls the real code from gitlab.
>

Yea, fun times that hack... :(

Warner