public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: pvorel@suse.cz, ltp@lists.linux.it
Cc: automated-testing@lists.yoctoproject.org
Subject: Re: [LTP] [Automated-testing] [RFC PATCH 1/3] runltp: Deprecate, add info about kirk
Date: Fri, 07 Jun 2024 15:50:14 +0100	[thread overview]
Message-ID: <8043628a6eed94e788f9fedbf6c8b264ebfbae15.camel@linuxfoundation.org> (raw)
In-Reply-To: <20240607142423.116285-2-pvorel@suse.cz>

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.

Cheers,

Richard



-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-06-07 14:50 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   ` Richard Purdie [this message]
2024-06-07 15:45     ` [LTP] [Automated-testing] " 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
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=8043628a6eed94e788f9fedbf6c8b264ebfbae15.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=automated-testing@lists.yoctoproject.org \
    --cc=ltp@lists.linux.it \
    --cc=pvorel@suse.cz \
    /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