[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run
From: |
Daniel P . Berrangé |
Subject: |
Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run |
Date: |
Wed, 9 Mar 2022 13:02:05 +0000 |
User-agent: |
Mutt/2.1.5 (2021-12-30) |
On Wed, Mar 09, 2022 at 01:50:34PM +0100, Philippe Mathieu-Daudé wrote:
> On 9/3/22 13:33, Daniel P. Berrangé wrote:
> > On Wed, Mar 09, 2022 at 12:58:42PM +0100, Thomas Huth wrote:
>
> > > Basically fine for me, but can we really run additional cirrus-ci jobs by
> > > default? IIRC the parallel execution of those were quite limited for the
> > > free tier, so did you look close that we don't run into additional
> > > timeouts
> > > yet, due to delayed cirrus-ci jobs?
> >
> > You can run 2 jobs in parallel in Cirrus. Beyond that they
> > get queued/serialized
> >
> > We have a 1 hour job timeout.
> >
> > We have to expect jobs will sometimes run slower than normal.
> >
> > IOW if we have a job on Cirrus taking 30 minutes normally, we
> > expect it will sometimes take 45 minutes.
> >
> > All this means that if we want Cirrus to be reliable and not
> > time out, we can really only have 2 jobs by default, unless
> > we can get the job execution time down to around 20 minutes
> > to allow for serialization.
> >
> > We used to have terrible problems with cirrus timeouts when
> > we were running 4 jobs concurrently (2 on staging and 2 on
> > master). We addressed that in 9968de0a4a5470bd7b98dcd2fae5d5269908f16b
> > by disabling the jobs on master.
> >
> > IOW, we really need to choose 1 macOS job and 1 FreeBSD job
> > and others need to be marked manual.
>
> Not sure which job to choose yet. Per the first google hits we
> still want to cover Catalina first:
> https://www.statista.com/statistics/944559/worldwide-macos-version-market-share/
My general gut feeling is usually to prioritize testing older versions
as they tend to be more widely used, and we want to avoid regresions
on stuff that has been around the longest. Compatibility problems with
new releases tend to get reported by users/maintainers and would not
be regressions, but rather enhancements to support the new platform.
But it is not really an easy decision, as clearly we would prefer to
test both old and new if we had the ability.
Having one as a nightly job is a reasonable compromise.
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 :|
- Re: [PATCH v7 20/22] ui/cocoa: capture all keys and combos when mouse is grabbed, (continued)
- [PATCH v7 21/22] ui/cocoa: add option to swap Option and Command, Philippe Mathieu-Daudé, 2022/03/06
- [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Philippe Mathieu-Daudé, 2022/03/06
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Philippe Mathieu-Daudé, 2022/03/09
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Thomas Huth, 2022/03/09
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Daniel P . Berrangé, 2022/03/09
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Philippe Mathieu-Daudé, 2022/03/09
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Thomas Huth, 2022/03/09
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Daniel P . Berrangé, 2022/03/09
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run,
Daniel P . Berrangé <=
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Peter Maydell, 2022/03/09
- Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Philippe Mathieu-Daudé, 2022/03/09
Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run, Daniel P . Berrangé, 2022/03/09
Re: [PATCH v7 00/22] host: Support macOS 12, Philippe Mathieu-Daudé, 2022/03/15