Re: [Buildroot] [PATCH 1/1] support/testing: ltp-testsuite: replace runltp by kirk

[Petr Vorel <petr.vorel@gmail.com>]

Hi Thomas,

> On Sun, 21 Dec 2025 19:08:10 +0100
> Julien Olivain via buildroot <buildroot@buildroot.org> wrote:

> > The run log of this ltp-testsuite test shows:

> >     INFO: runltp script is deprecated, try kirk
> >     https://github.com/linux-test-project/kirk

> > This commit updates this test to replace this deprecated runltp
> > shell script with the newer kirk Python script.

> > The logic of this runtime test remains the same: it runs a small number
> > of 'read' system call tests, and checks there is no failures and at
> > least one test succeed.

> > Cc: Petr Vorel <petr.vorel@gmail.com>
> > Signed-off-by: Julien Olivain <ju.o@free.fr>
> > ---
> > Patch tested in:
> > https://gitlab.com/jolivain/buildroot/-/jobs/12510635102
> > ---
> >  .../tests/package/test_ltp_testsuite.py       | 33 +++++++++++--------
> >  1 file changed, 20 insertions(+), 13 deletions(-)

> Thanks, I've applied.
+1, thanks!

> However, it's a bit of a pity that now Python 3
> is needed on the target to run LTP.

Yeah. I don't like it either. Specially LTP tests themselves does not require
anything (single test is either binary written in C statically linked LTP
libraries, we also have few POSIX compatible shell based tests which require
barely minimum of external dependencies), it can be run as is.

ATM we have list of tests in so called runtest files [1], which contain list of
tests (each line is single test: "test_label binary/script optional_arguments"),
therefore anything which can remove the first parameter and execute the rest can
be LTP runner. i.e. Buildroot custom script could be really minimal.

runltp does quite a few other things but these who need them should really move
to kirk. Also we plan to implement in kirk and ltx running tests in parallel.
That will save a lot of runtime.

[1] https://github.com/linux-test-project/ltp/tree/master/runtest

> One option would as suggested by Petr to use kirk in its intended mode,
> with kirk running on the host, and connected over SSH to the target to
> run tests.

> On the other hand, it was a lot more simple/convenient to be able to
> just run a simple shell script on the target to run the test suite.

Would it be possible to have both? Vendor runltp for local use and package kirk
as a host package (+ ltx as normal package)?

Kind regards,
Petr

> Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot