Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: Ricardo Martincoski <ricardo.martincoski@datacom.com.br>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC v1 1/1] support/testing/run-tests: add ability to run tests from external
Date: Sat, 23 Dec 2023 14:40:18 +0100	[thread overview]
Message-ID: <20231223144018.5dff2c0c@windsurf> (raw)
In-Reply-To: <20231222232251.12786-2-colin.foster@in-advantage.com>

Hello Colin,

On Fri, 22 Dec 2023 17:22:51 -0600
Colin Foster <colin.foster@in-advantage.com> wrote:

> +    overlay_path = os.getenv("BR2_EXTERNAL")
> +    if overlay_path:
> +        temp_dir = tempfile.TemporaryDirectory()
> +        shutil.copytree(script_dir, temp_dir.name, dirs_exist_ok=True)
> +        shutil.copytree(overlay_path + "/support/testing",
> +                        temp_dir.name,
> +                        dirs_exist_ok=True)

Is there a better solution than copying all tests into a temporary
directory?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-12-23 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 23:22 [Buildroot] [RFC v1 0/1] Add external test support Colin Foster
2023-12-22 23:22 ` [Buildroot] [RFC v1 1/1] support/testing/run-tests: add ability to run tests from external Colin Foster
2023-12-23 13:40   ` Thomas Petazzoni via buildroot [this message]
2023-12-23 16:12     ` Colin Foster
2023-12-23 13:54   ` Yann E. MORIN
2023-12-23 17:18     ` Colin Foster

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=20231223144018.5dff2c0c@windsurf \
    --to=buildroot@buildroot.org \
    --cc=colin.foster@in-advantage.com \
    --cc=ricardo.martincoski@datacom.com.br \
    --cc=thomas.petazzoni@bootlin.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