From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, f4bug@amsat.org,
pbonzini@redhat.com, stefanha@redhat.com, crosa@redhat.com,
Thomas Huth <thuth@redhat.com>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Beraldo Leal <bleal@redhat.com>
Subject: Re: [RFC PATCH] gitlab: shuffle some targets and reduce avocado noise
Date: Fri, 15 Sep 2023 18:09:41 +0200 [thread overview]
Message-ID: <20171390-43cc-ee15-128c-7e9b9892483a@linaro.org> (raw)
In-Reply-To: <20230915160358.615687-1-alex.bennee@linaro.org>
On 15/9/23 18:03, Alex Bennée wrote:
> We move a couple of targets out of the avocado runs because there are
> no tests to run. Tricore already has some coverage, for cris we make
> use of the fedora image we have and its own check-tcg tests.
>
> To reduce the noise of CANCEL messages we also set AVOCADO_TAGS
> appropriately so we filter down the number of tests we attempt.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
> .gitlab-ci.d/buildtest.yml | 26 ++++++++++++++++++++++----
> 1 file changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/.gitlab-ci.d/buildtest.yml b/.gitlab-ci.d/buildtest.yml
> index aee9101507..7813cb09a4 100644
> --- a/.gitlab-ci.d/buildtest.yml
> +++ b/.gitlab-ci.d/buildtest.yml
> @@ -30,6 +30,7 @@ avocado-system-alpine:
> variables:
> IMAGE: alpine
> MAKE_CHECK_ARGS: check-avocado
> + AVOCADO_TAGS: arch:avr arch:loongarch64 arch:mips64 arch:mipsel
Doh I never realized we weren't using AVOCADO_TAGS in CI, since this was
the point of adding it... I suppose the patchset was contributed half
way. Thanks for finishing the work here!
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
prev parent reply other threads:[~2023-09-15 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 16:03 [RFC PATCH] gitlab: shuffle some targets and reduce avocado noise Alex Bennée
2023-09-15 16:09 ` Philippe Mathieu-Daudé [this message]
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=20171390-43cc-ee15-128c-7e9b9892483a@linaro.org \
--to=philmd@linaro.org \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=wainersm@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).