From: Cyril Hrubis <chrubis@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [RFC][PATCH 0/2] Merge runtest files
Date: Thu, 3 Apr 2025 17:47:41 +0200 [thread overview]
Message-ID: <Z-6tnZLIQvY3IIbb@yuki.lan> (raw)
In-Reply-To: <0045063b-ae7f-4dd6-9b8e-9d760713ea3b@suse.com>
Hi!
> this is a _huge_ topic that might affect LTP automation configurations.
>
> It's a job that IMHO should be done, but it makes more sense to wait for
> testing suites definition in metadata, as well as a total refactoring of
> old LTP tests.
For a bigger changes yes. I would say that eliminating runtest files
with a single test could be done sooner.
> The reason of my statements is not only that runtest files should be
> removed one day, but also that known issues inside products which are
> tested, often require years of analysis of the runtest files and their
> executions. By shuffling tests around will create issues where there's
> no need due to a small logical improvement.
I do not think that it's as severe as you describe it. We change runtest
files a lot in each release and additions to runtest/syscall are the most
frequent.
> I think we should start to push more on testing suites definition inside
> metadata and to refactor tests as fast as possible. So we will be free
> from runtest files, leading to a more coherent structure of the tests
> organization.
We are getting there slowly, but I'm afraid that it will take years to
get there.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2025-04-03 15:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 10:19 [LTP] [RFC][PATCH 0/2] Merge runtest files Petr Vorel
2025-04-03 10:19 ` [LTP] [RFC][PATCH 1/2] runtest/ipc: Enable named pipes on non-blocking IO Petr Vorel
2025-04-06 2:55 ` Li Wang via ltp
2025-04-08 18:37 ` Cyril Hrubis
2025-04-03 10:19 ` [LTP] [RFC][PATCH 2/2] runtest: Move ipc into syscalls Petr Vorel
2025-04-06 3:01 ` Li Wang via ltp
2025-04-07 12:15 ` Petr Vorel
2025-04-07 12:19 ` Petr Vorel
2025-04-17 9:22 ` Cyril Hrubis
2025-04-17 11:14 ` Petr Vorel
2025-04-03 11:33 ` [LTP] [RFC][PATCH 0/2] Merge runtest files Andrea Cervesato via ltp
2025-04-03 15:47 ` Cyril Hrubis [this message]
2025-04-06 2:52 ` Li Wang via ltp
2025-04-06 2:43 ` Li Wang via ltp
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=Z-6tnZLIQvY3IIbb@yuki.lan \
--to=chrubis@suse.cz \
--cc=andrea.cervesato@suse.com \
--cc=ltp@lists.linux.it \
/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