All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: nvhieudt11@gmail.com, bitbake-devel@lists.openembedded.org
Cc: Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [bitbake-devel] [PATCH] Support add-layer to prepend
Date: Wed, 20 Mar 2024 23:15:54 +0000	[thread overview]
Message-ID: <9063a1127c8d569337ed4bea269b3168de780020.camel@linuxfoundation.org> (raw)
In-Reply-To: <HOgI.1707132673041693756.jdfH@lists.openembedded.org>

On Mon, 2024-02-05 at 03:31 -0800, nvhieudt11@gmail.com wrote:
> As you know, layer order in BBLAYERS can affect in parsing recipes process,
> in some cases, users want to add a layer on the top of BBLAYERS variable
>  
> So, add "--prepend" option for bitbake-layers to support add-layer to prepend
>  
> Signed-off-by: Hieu Van Nguyen <hieu2.nguyen@lge.com>
> ---
>  lib/bb/utils.py        | 7 +++++--
>  lib/bblayers/action.py | 3 ++-
>  2 files changed, 7 insertions(+), 3 deletions(-)


Unfortunately this patch has caused some really obscure build failures e.g.:

https://autobuilder.yoctoproject.org/typhoon/#/builders/80/builds/6487/steps/14/logs/stdio
and
https://autobuilder.yoctoproject.org/typhoon/#/builders/87/builds/6519/steps/14/logs/stdio

To prove it, you can in parallel run:

inotifywait . -m -e create -e access  ./recipes-devtools/makedevs/ ./recipes-devtools/ ./recipes-devtools/makedevs/makedevs/

on the meta directory and then in a different terminal:

oe-selftest -r devtool.DevtoolUpdateTests.test_devtool_update_recipe_local_files -j 2 -K

and what you'll see is:

./recipes-devtools/makedevs/makedevs/ CREATE makedevs.c
./recipes-devtools/makedevs/ CREATE makedevs_1.0.1.bb

amongst the accesses.

The devtool test code (meta/lib/oeqa/selftest/cases/devtool.py)
isolates it's changes to a copy of the meta directory using the
function you're chaging but this change stops that copy from working
correctly and breaks that isolation.

Cheers,

Richard


  parent reply	other threads:[~2024-03-20 23:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 11:31 [PATCH] Support add-layer to prepend nvhieudt11
2024-02-07 22:36 ` [bitbake-devel] " Alexandre Belloni
2024-02-19 16:51   ` nvhieudt11
2024-03-20 23:15 ` Richard Purdie [this message]
2024-03-28  6:49   ` nvhieudt11
2024-03-28 14:06     ` [bitbake-devel] " Peter Kjellerstedt
2024-03-28 14:56       ` nvhieudt11

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=9063a1127c8d569337ed4bea269b3168de780020.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexandre.belloni@bootlin.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=nvhieudt11@gmail.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.