From: Cyril Hrubis <chrubis@suse.cz>
To: Tim Bird <tim.bird@sony.com>
Cc: Don Zickus <dzickus@redhat.com>,
"workflows@vger.kernel.org" <workflows@vger.kernel.org>,
"automated-testing@lists.yoctoproject.org"
<automated-testing@lists.yoctoproject.org>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>,
kernelci <kernelci@lists.linux.dev>,
Nikolai Kondrashov <nkondras@redhat.com>,
Gustavo Padovan <gustavo.padovan@collabora.com>,
kernelci-members <kernelci-members@groups.io>,
"laura.nao@collabora.com" <laura.nao@collabora.com>
Subject: Re: [Automated-testing] [RFC] Test catalog template
Date: Wed, 16 Oct 2024 15:10:39 +0200 [thread overview]
Message-ID: <Zw-7Tydnaaj3XAQo@yuki.lan> (raw)
In-Reply-To: <MW5PR13MB5632C443F9D7E658168BC77DFD452@MW5PR13MB5632.namprd13.prod.outlook.com>
Hi!
> Just saying "LTP" is not granular enough. LTP has hundreds of individual
> test programs, and it would be useful to specify the individual tests
> from LTP that should be run per sub-system.
A few thousand tests to be more precise, and also the content tend to
change between releases, be it test additions or removal and I do not
think this level of changes is somehing that makes sense to be tracked
in such database.
It may be better to have more generic description of LTP subsets, there
are a few obvious e.g. "SysV IPC" or "Timers", and have the LTP
testrunner map that to actual testcases. The hard task here is to figure
out which groups would be useful and keep the set reasonably small.
I can move this forward in LTP reasonably quickly we get small list of
useful groups from kernel develpers.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2024-10-16 13:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 20:32 [RFC] Test catalog template Donald Zickus
2024-10-15 16:01 ` [Automated-testing] " Bird, Tim
2024-10-16 13:10 ` Cyril Hrubis [this message]
2024-10-16 18:02 ` Donald Zickus
2024-10-17 11:01 ` Cyril Hrubis
2024-10-16 18:00 ` Donald Zickus
2024-10-17 12:31 ` Minas Hambardzumyan
2024-10-18 19:44 ` Donald Zickus
2024-10-18 7:21 ` David Gow
2024-10-18 14:23 ` Gustavo Padovan
2024-10-18 14:35 ` [Automated-testing] " Cyril Hrubis
2024-10-18 19:17 ` Mark Brown
2024-10-18 20:17 ` Donald Zickus
2024-10-19 6:36 ` David Gow
2024-11-06 17:01 ` Donald Zickus
2024-11-20 8:16 ` David Gow
2024-11-21 15:28 ` Donald Zickus
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=Zw-7Tydnaaj3XAQo@yuki.lan \
--to=chrubis@suse.cz \
--cc=automated-testing@lists.yoctoproject.org \
--cc=dzickus@redhat.com \
--cc=gustavo.padovan@collabora.com \
--cc=kernelci-members@groups.io \
--cc=kernelci@lists.linux.dev \
--cc=laura.nao@collabora.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=nkondras@redhat.com \
--cc=tim.bird@sony.com \
--cc=workflows@vger.kernel.org \
/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