From: Alexander Kanavin <alex.kanavin@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: yocto@lists.yoctoproject.org
Subject: Re: [yocto] [yocto-autobuilder2][PATCH 2/2] config.py: include 32 bit qemux86-ptest (full) into a-full
Date: Wed, 14 Dec 2022 09:40:56 +0100 [thread overview]
Message-ID: <CANNYZj8zvJb6wwM+eFSxdj6MAJzGSFXQPWt_h+BwVoWkC=Fw8g@mail.gmail.com> (raw)
In-Reply-To: <3839f0c710cd4c57f60405bdf71cc451fd3d5084.camel@linuxfoundation.org>
On Tue, 13 Dec 2022 at 23:56, Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
> 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?
I don't have a strong opinion here. But what about qemux86-ptest-fast,
should that be in a-quick only, a-quick+a-full, or neither?
Alex
prev parent reply other threads:[~2022-12-14 8:41 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 ` [yocto] " Richard Purdie
2022-12-14 8:40 ` Alexander Kanavin [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='CANNYZj8zvJb6wwM+eFSxdj6MAJzGSFXQPWt_h+BwVoWkC=Fw8g@mail.gmail.com' \
--to=alex.kanavin@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--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.