Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Otavio Salvador" <otavio@ossystems.com.br>
Cc: <openembedded-core@lists.openembedded.org>,
	"Ricardo Salveti" <ricardo.salveti@oss.qualcomm.com>,
	"Paul Barker" <paul@pbarker.dev>
Subject: Re: [OE-core] [PATCH v2 3/3] checklayer: Share each world signature dump between the tests needing it
Date: Fri, 30 Oct 2026 08:05:27 +0100	[thread overview]
Message-ID: <DMHZD6V13WC0.2307BYF5XATFW@bootlin.com> (raw)
In-Reply-To: <179327642127.31634.6504288368028561565@ossystems.com.br>

On Thu Oct 29, 2026 at 1:20 PM CET, Otavio Salvador wrote:
> Hi Mathieu,
>
> I saw this patch was reverted in master-next to test Ricardo's
> "checklayer: run bitbake once per machine for the machine tests",
> since the two conflict. Ricardo replied that his patch solves the same
> issue and can be dropped in favour of this one:
>
> https://patchwork.yoctoproject.org/comment/42922/
>
> master-next still has the revert, with Ricardo's patch on top. Could
> you drop both, so this patch goes back in with 1/3 and 2/3? It covers
> the machine tests as his does, and the common tests too: test_world
> and test_signatures share one dump.
>
> If you'd rather keep Ricardo's version, I have a follow-up on top of
> it that moves the common tests to his cache, and I can send that
> instead.
>
> Thanks,
> Otavio

Hi Otavio,

This was discussed during yesterday review meeting: we believe we should
proceed with your version of the changes, possibly with some
improvements. So yes, I dropped Ricardo patch.

Thanks,
Mathieu

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


      reply	other threads:[~2026-10-30  7:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-17 22:56 [PATCH 0/3] yocto-check-layer: Faster BSP checks over many machines Otavio Salvador
2026-10-17 22:56 ` [PATCH 1/3] yocto-check-layer: Add --run-tests to select the tests to run Otavio Salvador
2026-10-19  8:19   ` Paul Barker
2026-10-17 22:56 ` [PATCH 2/3] yocto-check-layer: Skip initial signatures unless test_signatures runs Otavio Salvador
2026-10-17 22:56 ` [PATCH 3/3] checklayer: Reuse signatures of an identical successful world dump Otavio Salvador
2026-10-19  9:04   ` Paul Barker
2026-10-19 10:01     ` Paul Barker
2026-10-19 14:39 ` [PATCH v2 0/3] yocto-check-layer: Faster BSP checks over many machines Otavio Salvador
2026-10-19 14:39   ` [PATCH v2 1/3] yocto-check-layer: Add --run-tests to select the tests to run Otavio Salvador
2026-10-19 14:39   ` [PATCH v2 2/3] yocto-check-layer: Skip initial signatures unless test_signatures runs Otavio Salvador
2026-10-19 14:39   ` [PATCH v2 3/3] checklayer: Share each world signature dump between the tests needing it Otavio Salvador
2026-10-29 12:20     ` [OE-core] " Otavio Salvador
2026-10-30  7:05       ` Mathieu Dubois-Briand [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=DMHZD6V13WC0.2307BYF5XATFW@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=paul@pbarker.dev \
    --cc=ricardo.salveti@oss.qualcomm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox