Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Philippe Mathieu-Daudé
On 9/3/22 14:09, Peter Maydell wrote: On Wed, 9 Mar 2022 at 13:02, Daniel P. Berrangé wrote: On Wed, Mar 09, 2022 at 01:50:34PM +0100, Philippe Mathieu-Daudé wrote: Not sure which job to choose yet. Per the first google hits we still want to cover Catalina first:

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Peter Maydell
On Wed, 9 Mar 2022 at 13:02, Daniel P. Berrangé wrote: > > On Wed, Mar 09, 2022 at 01:50:34PM +0100, Philippe Mathieu-Daudé wrote: > > Not sure which job to choose yet. Per the first google hits we > > still want to cover Catalina first: > >

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Daniel P . Berrangé
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

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Daniel P . Berrangé
On Wed, Mar 09, 2022 at 01:52:15PM +0100, Thomas Huth wrote: > On 09/03/2022 13.50, Philippe Mathieu-Daudé wrote: > > > Would it be beneficial to have a 1 per OS job during PR, and > > other jobs run nightly (once a day, not per PR)? > > Is there a way to trigger nightly runs in gitlab? Yes, in

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Thomas Huth
On 09/03/2022 13.50, Philippe Mathieu-Daudé wrote: Would it be beneficial to have a 1 per OS job during PR, and other jobs run nightly (once a day, not per PR)? Is there a way to trigger nightly runs in gitlab? Thomas

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Philippe Mathieu-Daudé
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

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Daniel P . Berrangé
On Wed, Mar 09, 2022 at 12:58:42PM +0100, Thomas Huth wrote: > On 09/03/2022 11.24, Philippe Mathieu-Daudé wrote: > > Hi Alex, Thomas, Daniel, > > > > Could you ack this patch? > > Basically fine for me, but can we really run additional cirrus-ci jobs by > default? IIRC the parallel execution of

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Thomas Huth
On 09/03/2022 11.24, Philippe Mathieu-Daudé wrote: Hi Alex, Thomas, Daniel, Could you ack this patch? 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

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Daniel P . Berrangé
On Mon, Mar 07, 2022 at 12:17:53AM +0100, Philippe Mathieu-Daudé wrote: > From: Philippe Mathieu-Daudé > > Add support for macOS 12 build on Cirrus-CI, similarly to commit > 0e103a65ba1 ("gitlab: support for ... macOS 11 via cirrus-run"), > but with the following differences: > - Enable modules

Re: [PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-09 Thread Philippe Mathieu-Daudé
Hi Alex, Thomas, Daniel, Could you ack this patch? On 7/3/22 00:17, Philippe Mathieu-Daudé wrote: From: Philippe Mathieu-Daudé Add support for macOS 12 build on Cirrus-CI, similarly to commit 0e103a65ba1 ("gitlab: support for ... macOS 11 via cirrus-run"), but with the following differences:

[PATCH v7 22/22] gitlab-ci: Support macOS 12 via cirrus-run

2022-03-06 Thread Philippe Mathieu-Daudé
From: Philippe Mathieu-Daudé Add support for macOS 12 build on Cirrus-CI, similarly to commit 0e103a65ba1 ("gitlab: support for ... macOS 11 via cirrus-run"), but with the following differences: - Enable modules (configure --enable-modules) - Do not run softfloat3 tests (make check-softfloat)