public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Li Wang via ltp <ltp@lists.linux.it>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] LTP old API conversion
Date: Wed, 18 Mar 2026 13:18:07 +0800	[thread overview]
Message-ID: <abo1j7frPELV8-xb@redhat.com> (raw)
In-Reply-To: <abl0DkVFXKT-pS34@yuki.lan>

On Tue, Mar 17, 2026 at 04:32:30PM +0100, Cyril Hrubis wrote:
> Hi!
> > .. and tests conversion for tests which are smaller than 200 lines of code
> > requires minimal (if no) edit. I will continue to adapt the ltp-convert skill
> > in order to tweak and to improve this process for bigger tests.
> 
> I would disagree here withe the minimal edit. The old tests are quite
> often garbage. So the human in the process should asses if the test is
> actually doing anything useful and guide the machine to implement better
> test in a case that the original wasn't doing anything useful.
> 
> > ~~ Said so..
> > 
> > .. since this process seems to be quite straight forward, and with the usage
> > of LLM we could easily generate hundreds of patches per month, we don't really
> > want to flood the ML with garbage and to overwhelm who's involved into
> > maintenance review.
> 
> I'm pretty sure that you will get this down to smaller set as long as
> you actually spend some time thinking about what the test does. At least
> for me I'm able to spend 30% time on a test conversion because LLM, but
> you have to spend some time understanding what the test does and making
> sure it makes sense. Otherwise it's garbage in - garbage out.

Yes but not entirely. We can have AI summarize test methods within
code comments, which helps us grasp the underlying logic much faster
than reading through legacy code directly.

And, nowdays AI is gradually becoming the producer of code, while
humans(specifically maintainers) assume the role of the ultimate
guardians of code quality.

-- 
Regards,
Li Wang


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

      parent reply	other threads:[~2026-03-18  5:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-17 10:42 [LTP] LTP old API conversion Andrea Cervesato via ltp
2026-03-17 11:58 ` Petr Vorel
2026-03-17 12:14   ` Andrea Cervesato via ltp
2026-03-17 22:39     ` Petr Vorel
2026-03-18  5:36       ` Li Wang via ltp
2026-03-17 15:32 ` Cyril Hrubis
2026-03-17 15:49   ` Andrea Cervesato via ltp
2026-03-18 13:04     ` Andrea Cervesato via ltp
2026-03-18  5:18   ` Li Wang via ltp [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=abo1j7frPELV8-xb@redhat.com \
    --to=ltp@lists.linux.it \
    --cc=chrubis@suse.cz \
    --cc=liwang@redhat.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