U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: David Lechner <dlechner@baylibre.com>, Tom Rini <trini@konsulko.com>
Cc: Marek Vasut <marex@denx.de>, Simon Glass <sjg@chromium.org>,
	Mattijs Korpershoek <mkorpershoek@kernel.org>,
	Jerome Forissier <jerome.forissier@linaro.org>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Julien Stephan <jstephan@baylibre.com>,
	u-boot@lists.denx.de, David Lechner <dlechner@baylibre.com>
Subject: Re: [PATCH v2 0/3] a few test.py improvements
Date: Thu, 18 Dec 2025 11:59:30 +0100	[thread overview]
Message-ID: <87fr98cay5.fsf@kernel.org> (raw)
In-Reply-To: <20251217-a-few-test-py-improvements-v2-0-e1f91e3bf551@baylibre.com>

Hi David,

Thank you for the series

On Wed, Dec 17, 2025 at 12:42, David Lechner <dlechner@baylibre.com> wrote:

> While trying to run the test suite for the first time, I encountered a
> few minor issues. Here are a few patches to address them.
>
> ---
> Changes in v2:
> - Dropped patch adding setuptools to test/py/requirements.txt
> - New patch to add setuptools to scripts/dtc/pylibfdt/requirements.txt
>   instead.
> - Changed test.py patch to set ubconfig to None rather than checking for
>   its existence in globals().
> - Link to v1: https://lore.kernel.org/r/20251121-a-few-test-py-improvements-v1-0-bacb4148fb0d@baylibre.com

Tested on a fresh fedora container with:

$ python -m venv venv
$ source venv/bin/activate
$ pip install -r test/py/requirements.txt
$ pip install -r scripts/dtc/pylibfdt/requirements.txt

Then I could build and test with:

$ ./test/py/test.py --bd sandbox --build -k ut

Tested-by: Mattijs Korpershoek <mkorpershoek@kernel.org> # sandbox

Also, all patches look good to me, so:

Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>

>
> ---
> David Lechner (3):
>       test.py: check ubconfig exists before using it
>       doc: pytest: mention additional requirements for venv
>       pylibfdt: add requirements.txt for setuptools
>
>  doc/develop/pytest/usage.rst          | 4 ++++
>  scripts/dtc/pylibfdt/requirements.txt | 1 +
>  test/py/conftest.py                   | 5 +++--
>  3 files changed, 8 insertions(+), 2 deletions(-)
> ---
> base-commit: a333d9e59f6675c9541c34643f334dbf50898647
> change-id: 20251121-a-few-test-py-improvements-b91babfc3e05
>
> Best regards,
> -- 
> David Lechner <dlechner@baylibre.com>

      parent reply	other threads:[~2025-12-18 10:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 18:42 [PATCH v2 0/3] a few test.py improvements David Lechner
2025-12-17 18:42 ` [PATCH v2 1/3] test.py: check ubconfig exists before using it David Lechner
2025-12-27 14:52   ` Simon Glass
2025-12-17 18:42 ` [PATCH v2 2/3] doc: pytest: mention additional requirements for venv David Lechner
2025-12-27 14:52   ` Simon Glass
2025-12-17 18:42 ` [PATCH v2 3/3] pylibfdt: add requirements.txt for setuptools David Lechner
2025-12-27 14:52   ` Simon Glass
2025-12-18 10:59 ` Mattijs Korpershoek [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=87fr98cay5.fsf@kernel.org \
    --to=mkorpershoek@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jerome.forissier@linaro.org \
    --cc=jstephan@baylibre.com \
    --cc=marex@denx.de \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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