From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>, yocto@lists.yoctoproject.org
Subject: Re: [yocto] [yocto-autobuilder2][PATCH 2/2] config.py: include 32 bit qemux86-ptest (full) into a-full
Date: Tue, 13 Dec 2022 22:55:56 +0000 [thread overview]
Message-ID: <3839f0c710cd4c57f60405bdf71cc451fd3d5084.camel@linuxfoundation.org> (raw)
In-Reply-To: <20221213154056.370033-2-alex.kanavin@gmail.com>
On Tue, 2022-12-13 at 16:40 +0100, Alexander Kanavin wrote:
> The manually triggered test result is here:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/141/builds/1
>
> The execution time is similar to the 64 bit x86 full ptest, as valgrind has been excluded
> from the 32 bit set, so I believe we can afford to run this in the standard
> matrix for master-next tests.
>
> Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
> ---
> config.py | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/config.py b/config.py
> index e638099..711dd98 100644
> --- a/config.py
> +++ b/config.py
> @@ -88,7 +88,7 @@ trigger_builders_wait_quick = trigger_builders_wait_shared + [
> trigger_builders_wait_full = trigger_builders_wait_shared + [
> "qemumips-alt", "edgerouter-alt", "qemuppc-alt", "qemux86-world-alt",
> "oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-fedora", "oe-selftest-centos",
> - "qemux86-64-ptest", "qemux86-64-ltp", "qemuarm64-ptest", "qemuarm64-ltp",
> + "qemux86-64-ptest", "qemux86-64-ltp", "qemuarm64-ptest", "qemuarm64-ltp", "qemux86-ptest",
> "meta-intel", "meta-arm", "meta-aws", "meta-agl-core", "meta-virt"
> ]
>
> @@ -117,7 +117,6 @@ builders_others = [
> "oe-selftest-arm",
> "metrics",
> "qemuriscv32", "qemuriscv64", "qemuriscv64-ptest", "qemuppc64",
> - "qemux86-ptest",
> "auh"
> ]
I'm not sure I agree. Yes, we can do it but I'm not sure we should.
This test doesn't seem to be one which is showing regressions, given we
have a low number of issues despite never having run it. The day to day
patch review struggles with the volume of tests we're running without
adding the load this test needs to a-full.
We need to focus the tests on those which catch issues creeping into
the project and I'm not convinced this is one of them. Running this
test once or twice a month is probably all we need?
Cheers,
Richard
next prev parent reply other threads:[~2022-12-13 22:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 15:40 [yocto-autobuilder2][PATCH 1/2] config.py: include qemux86-ptest-fast (32 bit) in a-quick Alexander Kanavin
2022-12-13 15:40 ` [yocto-autobuilder2][PATCH 2/2] config.py: include 32 bit qemux86-ptest (full) into a-full Alexander Kanavin
2022-12-13 22:55 ` Richard Purdie [this message]
2022-12-14 8:40 ` [yocto] " Alexander Kanavin
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=3839f0c710cd4c57f60405bdf71cc451fd3d5084.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=yocto@lists.yoctoproject.org \
/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.