From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCHv2 1/4] pseudo: Simplify pseudo_client_ignore_path_chroot()
Date: Tue, 1 Dec 2020 01:20:13 +0000 [thread overview]
Message-ID: <61bfe4c0ea574d5c865e3640a26e06f0@XBOX03.axis.com> (raw)
In-Reply-To: <1f005e64f11edd73d83461290baf0805f886fa41.camel@linuxfoundation.org>
> -----Original Message-----
> From: Richard Purdie <richard.purdie@linuxfoundation.org>
> Sent: den 30 november 2020 12:47
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCHv2 1/4] pseudo: Simplify
> pseudo_client_ignore_path_chroot()
>
> Hi Peter,
>
> On Wed, 2020-11-25 at 14:48 +0100, Peter Kjellerstedt wrote:
> > This also plugs a memory leak in pseudo_client_ignore_path_chroot().
> >
> > Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
>
> I make no claim to understand what happened but I tried patches 1 and 2
> in a build over the weekend and with the first two present:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/79/builds/1602
> https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/1584
> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/1586
> https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/1610
>
> I then removed this one leaving only patch 2 and the build was fine.
>
> So there is something odd in this patch but I've not looked into what
> or why only selftest is affected.
>
> Cheers,
>
> Richard
I believe I have found the problem. I had missed the edge case where
two commas are specified immediately after each other, or there is a
leading/trailing comma. This would effectively cause pseudo to ignore
all paths. Thankfully the fix is trivial.
I have verified that I could repeat the oe-selftest problems for the
wic.Wic2 tests, and that they are back to working with my updated
code.
I will wait with sending an updated patch series until I have a
response regarding how you want me to handle the third patch in
the series (see my other mail from earlier today).
//Peter
next prev parent reply other threads:[~2020-12-01 1:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 13:48 [PATCHv2 0/4] Support symbolic links in paths in PSEUDO_IGNORE_PATHS Peter Kjellerstedt
2020-11-25 13:48 ` [PATCHv2 1/4] pseudo: Simplify pseudo_client_ignore_path_chroot() Peter Kjellerstedt
2020-11-30 11:47 ` [OE-core] " Richard Purdie
2020-12-01 1:20 ` Peter Kjellerstedt [this message]
2020-11-25 13:48 ` [PATCHv2 2/4] bitbake.conf: Add all layers (from BBLAYERS) to PSEUDO_IGNORE_PATHS Peter Kjellerstedt
2020-11-25 13:48 ` [PATCHv2 3/4] bitbake.conf: Canonicalize paths in PSEUDO_IGNORE_PATHS Peter Kjellerstedt
2020-11-26 14:47 ` [OE-core] " Richard Purdie
2020-11-26 20:38 ` Peter Kjellerstedt
2020-11-26 23:41 ` Richard Purdie
2020-11-30 17:44 ` Peter Kjellerstedt
2020-12-01 7:58 ` Richard Purdie
2020-11-25 13:48 ` [PATCHv2 4/4] wic: Pass canonicalized " Peter Kjellerstedt
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=61bfe4c0ea574d5c865e3640a26e06f0@XBOX03.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=openembedded-core@lists.openembedded.org \
--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