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

[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é <berrange@redhat.com> 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)
> > >  - 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 handling of
> > > differences like debug vs non-debug to the x86 CI jobs.
> > >
> > > The jobs are also generally running OK; they occasionally fail due to
> > > timeouts, which is likely because we're overloading the machine by
> > > asking it to run 4 CI jobs at once plus the ad-hoc CI.
> > >
> > > Remove the 'allow_failure' tag from all these jobs, and switch the
> > > s390x-alldbg, aarch64-all, s390x-tci and aarch64-tci jobs to manual.
> >
> > Why the difference in skipping  'alldbg' vs 'all'  ? Was that just
> > to get diverse coverage of debug vs non-debug ?
> 
> Yeah, I figured we might as well run one on each.

Makes sense, in that case

  Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

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