From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Cleber Rosa" <crosa@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure
Date: Mon, 13 Sep 2021 11:35:29 +0100 [thread overview]
Message-ID: <CAFEAcA8-xkmZuBQRUjSxuJPbxaOyJGYpqTKCnz9D=cZTP8wa3Q@mail.gmail.com> (raw)
In-Reply-To: <YT8n3HKfbheSjuzn@redhat.com>
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.
thanks
-- PMM
next prev parent reply other threads:[~2021-09-13 10:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 10:19 [PATCH] gitlab-ci: Make more custom runner jobs manual, and don't allow failure Peter Maydell
2021-09-13 10:28 ` Daniel P. Berrangé
2021-09-13 10:35 ` Peter Maydell [this message]
2021-09-13 10:40 ` Daniel P. Berrangé
2021-09-13 15:28 ` Willian Rampazzo
2021-09-14 5:44 ` Thomas Huth
2021-09-14 16:03 ` Peter Maydell
2021-09-14 19:17 ` Peter Maydell
2021-09-14 20:03 ` Willian Rampazzo
2021-09-15 8:29 ` Daniel P. Berrangé
2021-09-15 8:40 ` Philippe Mathieu-Daudé
2021-09-15 12:12 ` Peter Maydell
2021-09-15 12:16 ` Daniel P. Berrangé
2021-09-15 12:22 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFEAcA8-xkmZuBQRUjSxuJPbxaOyJGYpqTKCnz9D=cZTP8wa3Q@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.