Re: [PATCH] cirrus.yml: Cover SPICE in the MSYS2 job

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

On Wed, Mar 22, 2023 at 01:13:21PM +0100, Philippe Mathieu-Daudé wrote:
> On 22/3/23 12:30, Thomas Huth wrote:
> > On 22/03/2023 12.05, Philippe Mathieu-Daudé wrote:
> > > Include the mingw-w64-x86_64-spice package so SPICE is covered:
> > > 
> > >    C compiler for the host machine: cc -m64 -mcx16 (gcc 12.2.0 "cc
> > > (Rev10, Built by MSYS2 project) 12.2.0")
> > >    ...
> > >    Run-time dependency spice-protocol found: YES 0.14.4
> > >    Run-time dependency spice-server found: YES 0.15.1
> > > 
> > > In particular this would have helped catching the build issue
> > > reported as https://gitlab.com/qemu-project/qemu/-/issues/1553:
> > 
> > Well, hardly anybody is looking at the output on cirrus-ci.com, so this
> > patch here likely would not have prevented the merging of this bug...
> > for that, you rather have to add it to .gitlab-ci.d/windows.yml instead.
> 
> It seems we have 2 jobs doing the same testing (even same version,
> msys2-base-x86_64-20220603.sfx.exe). Does it make sense to maintain
> both? At least with GitLab we notice a failure.

IMHO having the .cirrus.yml file can probably be considered actively
harmful.  Cirrus CI has a concurrency limit of 2 jobs, and when we
trigger Cirrus jobs from GitLab CII using cirrus-run, we need them
to completely in < 1 hour.

If we have extra jobs being triggered by the .cirrus.yml file when
gitlab.com repo is mirrored to github.com, then we're liable to
cause timeouts of the jobs we do care about from cirrus-run.

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