From: "Alexandre Belloni" <alexandre.belloni@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Ross Burton <ross@burtonini.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] util-linux: use the system binaries when running ptest
Date: Tue, 29 Jun 2021 08:52:28 +0200 [thread overview]
Message-ID: <YNrDLD4XfP2lPEe/@piout.net> (raw)
In-Reply-To: <9e0cd3d79c36f2b061cf2d751c8b544efffc23b2.camel@linuxfoundation.org>
On 28/06/2021 23:51:13+0100, Richard Purdie wrote:
> On Mon, 2021-06-28 at 14:01 +0100, Ross Burton wrote:
> > Unless told otherwise, the util-linux test suite assumes that it is
> > running in a build tree and looks for binaries to run.
> >
> > In ptest we're on the target, so it needs to run the system binaries
> > instead.
> >
> > This reduces ~180 skipped test cases down to tens, and should fix weird
> > behaviour. There are some new failures that were previously skipped
> > which will be investigated shortly.
> >
> > Also pass --parsable to reduce the amount of noise in the log ouput.
> >
> > [ YOCTO #14244 ]
> >
> > Signed-off-by: Ross Burton <ross.burton@arm.com>
> > ---
> > meta/recipes-core/util-linux/util-linux/run-ptest | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-core/util-linux/util-linux/run-ptest b/meta/recipes-core/util-linux/util-linux/run-ptest
> > index e135ee583bd..86f9fef24bd 100644
> > --- a/meta/recipes-core/util-linux/util-linux/run-ptest
> > +++ b/meta/recipes-core/util-linux/util-linux/run-ptest
> > @@ -29,7 +29,7 @@ res=0
> > count=0
> > for ts in $comps;
> > do
> > - $ts | sed -u '{
> > + $ts --use-system-commands --parsable | sed -u '{
> > s/^\(.*\):\(.*\) \.\.\. OK$/PASS: \1:\2/
> > s/^\(.*\):\(.*\) \.\.\. FAILED \(.*\)$/FAIL: \1:\2 \3/
> > s/^\(.*\):\(.*\) \.\.\. SKIPPED \(.*\)$/SKIP: \1:\2 \3/
>
> This is a good fix, thanks. Makes me worry about regression identification.
> FWIW testing showed this on x86 (arm still going):
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2227
>
Indeed, this one has the same issue:
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/2228/steps/12/logs/stdio
> Looks like a build from Alex did have results for arm:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1942/steps/12/logs/stdio
>
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-06-29 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 13:01 [PATCH] util-linux: use the system binaries when running ptest Ross Burton
2021-06-28 22:51 ` [OE-core] " Richard Purdie
2021-06-29 6:52 ` Alexandre Belloni [this message]
2021-06-29 11:25 ` Ross Burton
2021-06-29 12:28 ` Richard Purdie
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=YNrDLD4XfP2lPEe/@piout.net \
--to=alexandre.belloni@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross@burtonini.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.