From: Petr Vorel <petr.vorel@gmail.com>
To: Maxim Tarelov <tarelovma@yandex.ru>
Cc: buildroot@buildroot.org, Julien Olivain <ju.o@free.fr>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/ltp-testsuite: kirk needs python3
Date: Fri, 16 Jan 2026 07:35:55 +0100 [thread overview]
Message-ID: <20260116063555.GB554275@pevik> (raw)
In-Reply-To: <20260114192413.569151-1-tarelovma@yandex.ru>
Hi,
[ Cc Julien and Thomas ]
> LTP project contains a number of scripts, such as kirk, which depend on
> python3, but not all boards _defconfigs enable python3 by default.
> To avoid errors like this:
> # /usr/lib/ltp-testsuite/kirk
> env: can't execute 'python3': No such file or directory
> we must explicitly enable python3 when selecting LTP.
> Signed-off-by: Maxim Tarelov <tarelovma@yandex.ru>
> ---
> package/ltp-testsuite/Config.in | 1 +
> package/ltp-testsuite/ltp-testsuite.mk | 2 ++
> 2 files changed, 3 insertions(+)
> diff --git a/package/ltp-testsuite/Config.in b/package/ltp-testsuite/Config.in
> index 81dc9dffee..0ddc2fe02c 100644
> --- a/package/ltp-testsuite/Config.in
> +++ b/package/ltp-testsuite/Config.in
> @@ -15,6 +15,7 @@ config BR2_PACKAGE_LTP_TESTSUITE
> depends on BR2_PACKAGE_LTP_TESTSUITE_ARCH_SUPPORTS
> select BR2_PACKAGE_LIBTIRPC if !BR2_TOOLCHAIN_HAS_NATIVE_RPC
> select BR2_PACKAGE_MUSL_FTS if !BR2_TOOLCHAIN_USES_GLIBC
> + select BR2_PACKAGE_PYTHON3
I would prefer not to drag python3 for all people which want LTP.
There are a different ways to use LTP.
1) Preferred way to use kirk is to run it remotely. The main advantage is to to
detect test crashed the kernel, actually one of the reasons why we wrote kirk.
Also to reduce dependencies on SUT.
2) Run a single test (user wants to test sinle kernel/libc fix). Any LTP test
can be run just by executing it. Any runner (kirk or the old script runltp) is
to help using runtest files (and help with other tasks).
Moreover Buildroot has support/testing/tests/package/test_ltp_testsuite.py
where Julien adds kirk + BR2_PACKAGE_PYTHON3=y [1].
If this must be added differently, maybe a new option: "run kirk locally"
which would drag python3.
Also, I'm not sure if people are aware of support scripts (I did not know),
but I don't think anything can be done for it.
Kind regards,
Petr
[1] https://lore.kernel.org/buildroot/20251221180810.3770181-1-ju.o@free.fr/
> help
> The Linux Test Project provides a huge testsuite for Linux.
> diff --git a/package/ltp-testsuite/ltp-testsuite.mk b/package/ltp-testsuite/ltp-testsuite.mk
> index e4e3ff8717..c103ac9819 100644
> --- a/package/ltp-testsuite/ltp-testsuite.mk
> +++ b/package/ltp-testsuite/ltp-testsuite.mk
> @@ -13,6 +13,8 @@ LTP_TESTSUITE_LICENSE_FILES = COPYING
> LTP_TESTSUITE_CONF_OPTS += --disable-metadata
> +LTP_TESTSUITE_DEPENDENCIES += python3
> +
> ifeq ($(BR2_PACKAGE_LTP_TESTSUITE_OPEN_POSIX),y)
> LTP_TESTSUITE_CONF_OPTS += --with-open-posix-testsuite
> endif
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-01-16 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 19:24 [Buildroot] [PATCH 1/1] package/ltp-testsuite: kirk needs python3 Maxim Tarelov
2026-01-16 6:35 ` Petr Vorel [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=20260116063555.GB554275@pevik \
--to=petr.vorel@gmail.com \
--cc=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=tarelovma@yandex.ru \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.