Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>
To: alex.kanavin@gmail.com
Cc: openembedded-core@lists.openembedded.org,
	Alexander Kanavin <alex@linutronix.de>
Subject: Re: [OE-core] [PATCH 1/2] bitbake.conf: add an addfragments directive for oe-core and dependent layers
Date: Fri, 15 Nov 2024 13:44:14 +0100	[thread overview]
Message-ID: <ZzdCHndPtezHmT75@bootlin-mathieu> (raw)
In-Reply-To: <20241114111100.2624737-1-alex.kanavin@gmail.com>

On Thu, Nov 14, 2024 at 12:10:59PM +0100, Alexander Kanavin via lists.openembedded.org wrote:
> From: Alexander Kanavin <alex@linutronix.de>
> 
> Please see the patch to bitbake for syntax and implementation details.
> 
> The path prefix to fragments is in its own variable so it doesn't have
> to be hardcoded into tools.
> 
> Signed-off-by: Alexander Kanavin <alex@linutronix.de>
> ---

Hi Alexander,

I'm not sure what is the issue, but it looks like this patch is breaking
the patchtest-selftest on the autobuilder: the remove layers step is
timing out.

https://valkyrie.yoctoproject.org/#/builders/71/builds/431

Can you have a look at this issue ?

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  parent reply	other threads:[~2024-11-15 12:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14 11:10 [PATCH 1/2] bitbake.conf: add an addfragments directive for oe-core and dependent layers Alexander Kanavin
2024-11-14 11:11 ` [PATCH 2/2] bitbake-config-build: add a plugin for config fragments Alexander Kanavin
2024-11-14 11:16   ` Patchtest results for " patchtest
2024-11-14 13:20   ` [OE-core] " Mathieu Dubois-Briand
2024-11-14 13:33     ` Alexander Kanavin
2024-11-15 12:44 ` Mathieu Dubois-Briand [this message]
2024-11-15 14:52   ` [OE-core] [PATCH 1/2] bitbake.conf: add an addfragments directive for oe-core and dependent layers Alexander Kanavin

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=ZzdCHndPtezHmT75@bootlin-mathieu \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.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