On Tue, 22 Oct 2019 at 20:20, Alex Bennée <alex.ben...@linaro.org> wrote: > > The MacOS build can time out on Cirrus running to almost an hour. > Reduce the scope to the historical MacOS architectures much the same > way we do on Travis. > > Signed-off-by: Alex Bennée <alex.ben...@linaro.org> > --- > .cirrus.yml | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > > diff --git a/.cirrus.yml b/.cirrus.yml > index 8326a3a4b16..4b042c0e12c 100644 > --- a/.cirrus.yml > +++ b/.cirrus.yml > @@ -1,5 +1,6 @@ > env: > CIRRUS_CLONE_DEPTH: 1 > + MACOS_ARCHES: > i386-softmmu,ppc-softmmu,ppc64-softmmu,m68k-softmmu,x86_64-softmmu
I don't know whether Cirrus is our long-term plan for doing CI of OSX (maybe we'll be using Gitlab and some runner on an OSX platform??), but as a general point: since OSX is one of the non-Linux hosts it's therefore worth making sure our compile-coverage is as wide as possible, not narrow. It's safe(r) to have narrow coverage of x86-Linux because people catch issues with that anyway, but it's exactly the less common platforms like OSX, the BSDs, odd architectures that we want to be compile/make-check testing as much of our code as possible. thanks -- PMM
