Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-15 Thread Peter Maydell
On Wed, 15 Sept 2021 at 13:16, Daniel P. Berrangé wrote: > > On Wed, Sep 15, 2021 at 01:12:23PM +0100, Peter Maydell wrote: > > On Wed, 15 Sept 2021 at 09:29, Daniel P. Berrangé > > wrote: > > > Urgh, my bad, I completely forget this behaviour when reviewing. > > > When we only have > > > > > >

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-15 Thread Daniel P . Berrangé
On Wed, Sep 15, 2021 at 01:12:23PM +0100, Peter Maydell wrote: > On Wed, 15 Sept 2021 at 09:29, Daniel P. Berrangé wrote: > > Urgh, my bad, I completely forget this behaviour when reviewing. > > When we only have > > > > when: manual > > > > then the job has to be manually started, and it still

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-15 Thread Peter Maydell
On Wed, 15 Sept 2021 at 09:29, Daniel P. Berrangé wrote: > Urgh, my bad, I completely forget this behaviour when reviewing. > When we only have > > when: manual > > then the job has to be manually started, and it still contributes > to pipeline status, so it /must/ triggered manually. > > If we

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-15 Thread Philippe Mathieu-Daudé
On 9/15/21 10:29 AM, Daniel P. Berrangé wrote: > On Tue, Sep 14, 2021 at 08:17:19PM +0100, Peter Maydell wrote: >> On Mon, 13 Sept 2021 at 11:19, Peter Maydell >> wrote: >>> >>> Currently we define a lot of jobs for our custom runners: >>> for both aarch64 and s390x we have >>> - all-linux-stati

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-15 Thread Daniel P . Berrangé
On Tue, Sep 14, 2021 at 08:17:19PM +0100, Peter Maydell wrote: > On Mon, 13 Sept 2021 at 11:19, Peter Maydell wrote: > > > > Currently we define a lot of jobs for our custom runners: > > for both aarch64 and s390x we have > > - all-linux-static > > - all > > - alldbg > > - clang (manual) > >

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-14 Thread Willian Rampazzo
On Tue, Sep 14, 2021 at 4:18 PM Peter Maydell wrote: > > On Mon, 13 Sept 2021 at 11:19, Peter Maydell wrote: > > > > Currently we define a lot of jobs for our custom runners: > > for both aarch64 and s390x we have > > - all-linux-static > > - all > > - alldbg > > - clang (manual) > > - tci >

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-14 Thread Peter Maydell
On Mon, 13 Sept 2021 at 11:19, Peter Maydell wrote: > > Currently we define a lot of jobs for our custom runners: > for both aarch64 and s390x we have > - all-linux-static > - all > - alldbg > - clang (manual) > - tci > - notcg (manual) > > This is overkill. The main reason to run on these

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-14 Thread Peter Maydell
On Mon, 13 Sept 2021 at 11:19, Peter Maydell wrote: > > Currently we define a lot of jobs for our custom runners: > for both aarch64 and s390x we have > - all-linux-static > - all > - alldbg > - clang (manual) > - tci > - notcg (manual) > > This is overkill. The main reason to run on these

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-13 Thread Thomas Huth
On 13/09/2021 12.19, Peter Maydell wrote: Currently we define a lot of jobs for our custom runners: for both aarch64 and s390x we have - all-linux-static - all - alldbg - clang (manual) - tci - notcg (manual) This is overkill. The main reason to run on these hosts is to get coverage

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-13 Thread Willian Rampazzo
On Mon, Sep 13, 2021 at 7:22 AM Peter Maydell wrote: > > Currently we define a lot of jobs for our custom runners: > for both aarch64 and s390x we have > - all-linux-static > - all > - alldbg > - clang (manual) > - tci > - notcg (manual) > > This is overkill. The main reason to run on these

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-13 Thread Daniel P . Berrangé
On Mon, Sep 13, 2021 at 11:35:29AM +0100, Peter Maydell wrote: > On Mon, 13 Sept 2021 at 11:32, Daniel P. Berrangé wrote: > > > > On Mon, Sep 13, 2021 at 11:19:48AM +0100, Peter Maydell wrote: > > > Currently we define a lot of jobs for our custom runners: > > > for both aarch64 and s390x we have

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-13 Thread Peter Maydell
On Mon, 13 Sept 2021 at 11:32, Daniel P. Berrangé wrote: > > On Mon, Sep 13, 2021 at 11:19:48AM +0100, Peter Maydell wrote: > > Currently we define a lot of jobs for our custom runners: > > for both aarch64 and s390x we have > > - all-linux-static > > - all > > - alldbg > > - clang (manual) >

Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-13 Thread Daniel P . Berrangé
On Mon, Sep 13, 2021 at 11:19:48AM +0100, Peter Maydell wrote: > Currently we define a lot of jobs for our custom runners: > for both aarch64 and s390x we have > - all-linux-static > - all > - alldbg > - clang (manual) > - tci > - notcg (manual) > > This is overkill. The main reason to run

[PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure

2021-09-13 Thread Peter Maydell
Currently we define a lot of jobs for our custom runners: for both aarch64 and s390x we have - all-linux-static - all - alldbg - clang (manual) - tci - notcg (manual) This is overkill. The main reason to run on these hosts is to get coverage for the host architecture; we can leave the handl