Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: "Ayoub Zaki" <ayoub.zaki@embetrix.com>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [wrynose][PATCH] oeqa/selftest/devtool: handle existing patch directories in recipe tests
Date: Tue, 20 Oct 2026 11:33:56 +0200	[thread overview]
Message-ID: <DM9K9FJ3GUXI.2GAS3HOWNI97V@smile.fr> (raw)
In-Reply-To: <20261019125810.492968-1-ayoub.zaki@embetrix.com>

On Mon Oct 19, 2026 at 2:58 PM CEST, Ayoub Zaki wrote:
> Recipe update and finish tests assume generated patches live in a
> directory named after the recipe. Existing files/ or versioned directories
> can instead cause staging failures and leave generated files for later
> tests. Cleanup can also delete tracked patches that should be preserved.
>
> Share recipe-directory cleanup that resets the index, removes untracked
> files and restores tracked files. Stage recipe changes and check generated
> patch filenames without assuming a subdirectory, including the
> --initial-rev cases. Keep paths that describe known fixture contents.
>
> Validated with devtool.DevtoolUpdateTests.test_devtool_update_recipe and
> isolated staging and cleanup checks on both target branches.
>
> AI-Generated: Uses OpenAI Codex
> Signed-off-by: Ayoub Zaki <ayoub.zaki@embetrix.com>
> ---
>  meta/lib/oeqa/selftest/cases/devtool.py | 65 +++++++++++++------------
>  1 file changed, 35 insertions(+), 30 deletions(-)

Hello,

This needs to be sent to master first. Then, blacksail.

Regards,
-- 
Yoann Congal
Smile ECS


      reply	other threads:[~2026-10-20  9:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 12:58 [wrynose][PATCH] oeqa/selftest/devtool: handle existing patch directories in recipe tests Ayoub Zaki
2026-10-20  9:33 ` Yoann Congal [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=DM9K9FJ3GUXI.2GAS3HOWNI97V@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=ayoub.zaki@embetrix.com \
    --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