Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: Julien Olivain via buildroot <buildroot@buildroot.org>,
	 Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] support/testing: ltp-testsuite: replace runltp by kirk
Date: Thu, 15 Jan 2026 20:47:33 +0100	[thread overview]
Message-ID: <aWlEAhChn8gSm7QZ@windsurf> (raw)
In-Reply-To: <20251230174958.GA496221@pevik>

Hello,

On Tue, Dec 30, 2025 at 06:49:58PM +0100, Petr Vorel wrote:

> 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.

I don't think I would want Buildroot to carry its own custom script
for this.

> 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)?

I'm not sure what you're suggesting as "both"? Do you mean, having a
simple test runner that we can run directly on the target, but also
offer the possibility of building/installing kirk to run the test
suite from the host?

I'm not sure what ltx is in this context.

Best regards,

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:[~2026-01-15 19:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-21 18:08 [Buildroot] [PATCH 1/1] support/testing: ltp-testsuite: replace runltp by kirk Julien Olivain via buildroot
2025-12-24  0:14 ` Petr Vorel
2025-12-28 22:20 ` Thomas Petazzoni via buildroot
2025-12-30 17:49   ` Petr Vorel
2026-01-15 19:47     ` Thomas Petazzoni via buildroot [this message]
2026-01-16  6:23       ` Petr Vorel
2026-01-07 17:50 ` Arnout Vandecappelle via buildroot

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=aWlEAhChn8gSm7QZ@windsurf \
    --to=buildroot@buildroot.org \
    --cc=ju.o@free.fr \
    --cc=petr.vorel@gmail.com \
    --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