Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: richard.purdie@linuxfoundation.org,
	Chen Qi <Qi.Chen@windriver.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][PATCH] selftest: allow '-R' and '-r' be used together
Date: Mon, 26 Dec 2022 09:33:59 +0100	[thread overview]
Message-ID: <Y6lcdwf2L70Rw1fM@mail.local> (raw)
In-Reply-To: <95441494-5a98-6831-3897-83e58dec8fff@windriver.com>

On 25/12/2022 19:13:43-0500, Randy MacLeod wrote:
> On 2022-11-25 08:00, Richard Purdie via lists.openembedded.org wrote:
> > Hi Qi,
> > 
> > On Fri, 2022-11-25 at 05:56 +0000, Chen Qi wrote:
> > > The AB is actually running 'all' tests.
> > > 
> > > The '--skip-tests (-R)' option means 'Run all (unhidden) tests except
> > > the ones specified.', according to its help message. This is also its
> > > actual effect for now. You can see there's an implicit 'run all
> > > tests' meaning in this option.
> > > The '-T (--exclude-tag)' options means 'Exclude all (unhidden) tests
> > > that match any of the specified tag(s)', according to its help
> > > message.
> > > 
> > > So the AB's oe-selftest command means: execute all tests except the
> > > ones tagged with 'machine' and 'toolchain-user', and also skip
> > > 'distrodata.Distrodata.test_checkpkg
> > > buildoptions.SourceMirroring.test_yocto_source_mirror reproducible'.
> > 
> > You're right, a different build has -t machine and I'm confusing the
> > two, sorry.
> > 
> > I don't really like making changes which require lockstep changes to
> > the autobuilder configuration but I can see why we could do with doing
> > so here.
> > 
> > I was thinking there should be symettry between -r and -R like there is
> > with -T and -t but that also probably doesn't make sense when you think
> > about it more.
> > 
> > Alex: We'll probably have to work out how to make this change...
> 
> Nudge and Happy Holidays.

Yes, this is still on my radar.


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      reply	other threads:[~2022-12-26  8:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24  2:55 [OE-core][PATCH] selftest: allow '-R' and '-r' be used together Chen Qi
2022-11-24 11:35 ` Alexandre Belloni
2022-11-24 12:24   ` Chen, Qi
2022-11-24 13:02     ` Alexandre Belloni
2022-11-24 13:10       ` Chen, Qi
2022-11-24 13:35         ` Alexandre Belloni
2022-11-24 13:47           ` Richard Purdie
2022-11-25  5:56             ` Chen, Qi
2022-11-25 13:00               ` Richard Purdie
2022-12-26  0:13                 ` Randy MacLeod
2022-12-26  8:33                   ` Alexandre Belloni [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=Y6lcdwf2L70Rw1fM@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=Qi.Chen@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox