From: Petr Vorel <pvorel@suse.cz>
To: Tim Orling <ticotimo@gmail.com>
Cc: ltp@lists.linux.it, automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [Automated-testing] [RFC PATCH 1/3] runltp: Deprecate, add info about kirk
Date: Mon, 10 Jun 2024 21:54:21 +0200 [thread overview]
Message-ID: <20240610195421.GA790951@pevik> (raw)
In-Reply-To: <CANx9H-C5KiqhVEp+Dysydsx8Kwvcy3VO+vSEfxWRFSeLEA47Ug@mail.gmail.com>
> On Fri, Jun 7, 2024 at 7:50 AM Richard Purdie via lists.yoctoproject.org
> <richard.purdie=linuxfoundation.org@lists.yoctoproject.org> wrote:
> > On Fri, 2024-06-07 at 16:24 +0200, Petr Vorel via
> > lists.yoctoproject.org wrote:
> > > kirk is not perfect but already much better than old runltp script.
> > > Let's deprecate runltp and propagate kirk.
> > > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > > ---
> > > runltp | 13 +++++++++++++
> > > 1 file changed, 13 insertions(+)
> > I'd note that Yocto Project's CI is still using runltp and we have no
> > recipe for kirk, or any experience of using it. This does therefore
> > worry me a little bit, there appears to be a lot of complexity in kirk
> > we don't need.
> I have begun a recipe for kirk. I know very little about the rest of how we
> (Yocto Project) run ltp or how kirk is meant to be used.
> https://git.yoctoproject.org/poky-contrib/log/?h=timo/kirk
+1. Maybe Richard or other people who did LTP update in Yocto in the past?
BTW we've just released kirk 1.3 (1.2 + few, but quite important ssh related
functional fixes). Please ideally use 998df1a5aa5026c5c9b91b0caa3b1188146aa678
(hash for 1.3).
Kind regards,
Petr
> > Cheers,
> > Richard
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2024-06-10 19:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 14:24 [LTP] [RFC PATCH 0/3] Deprecate runltp (please use kirk) Petr Vorel
2024-06-07 14:24 ` [LTP] [RFC PATCH 1/3] runltp: Deprecate, add info about kirk Petr Vorel
2024-06-07 14:50 ` [LTP] [Automated-testing] " Richard Purdie
2024-06-07 15:45 ` Cyril Hrubis
2024-06-07 16:08 ` Richard Purdie
2024-06-07 16:28 ` Bird, Tim
2024-06-07 16:48 ` Cyril Hrubis
2024-06-07 16:35 ` Cyril Hrubis
2024-06-07 17:00 ` Richard Purdie
2024-06-07 17:33 ` Cyril Hrubis
2024-06-07 21:17 ` Bird, Tim
2024-06-10 7:14 ` Andrea Cervesato via ltp
2024-06-10 15:32 ` Bird, Tim
2024-06-10 16:14 ` Petr Vorel
2024-06-11 12:28 ` Cyril Hrubis
2024-06-11 8:42 ` Cyril Hrubis
2024-06-10 9:22 ` Cyril Hrubis
2024-06-10 15:51 ` Bird, Tim
2024-06-10 16:54 ` Petr Vorel
2024-06-10 16:55 ` Petr Vorel
[not found] ` <17D79A236EC1FFC3.15678@lists.yoctoproject.org>
2024-06-12 7:53 ` Cyril Hrubis
2024-07-08 9:26 ` Petr Vorel
2024-06-08 20:32 ` Tim Orling
2024-06-10 19:54 ` Petr Vorel [this message]
2024-08-28 9:02 ` [LTP] " Cyril Hrubis
2024-08-28 12:31 ` Petr Vorel
2024-06-07 14:24 ` [LTP] [RFC PATCH 2/3] ltpmenu: Remove legacy script Petr Vorel
2024-08-28 8:52 ` Cyril Hrubis
2024-06-07 14:24 ` [LTP] [RFC PATCH 3/3] doc/old: Remove man pages Petr Vorel
2024-08-28 8:56 ` Cyril Hrubis
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=20240610195421.GA790951@pevik \
--to=pvorel@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=ltp@lists.linux.it \
--cc=ticotimo@gmail.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