From: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 6/8] lib/igt_kmod: place KUnit tests on a subtest
Date: Tue, 6 Jun 2023 15:57:27 +0200 [thread overview]
Message-ID: <20230606155727.032e0fa3@maurocar-mobl2> (raw)
In-Reply-To: <4686292.rnE6jSC6OK@jkrzyszt-mobl2.ger.corp.intel.com>
On Tue, 06 Jun 2023 12:03:04 +0200
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> wrote:
> > > > > > + igt_subtest_with_dynamic("all-tests")
> > > > >
> > > > > Why can't we use module_name as subtest name?
> > > >
> > > > We can, but this preserves the old behavior. So, the existing
> documentation
> > > > won't break.
> > >
> > > Where is this old behavior documented? In the current code I can't find
> any
> > > occurrence of "test-all" other than inside igt_kmod.c:igt_ksleftest(), not
> > > documented in any way.
> > >
> > > Wasn't the old behavior a result of a limitation rather than a feature?
> >
> > Take a look at igt_kselftests():
> >
> > igt_subtest_with_dynamic(filter ?: "all-tests") {
> > igt_list_for_each_entry_safe(tl, tn, &tests, link) {
> > unsigned long taints;
> >
> > igt_dynamic_f("%s", unfilter(filter, tl->name))
> > igt_kselftest_execute(&tst, tl, options,
> result);
> > free(tl);
> >
> > The default when "filter" is not used is "all-tests".
>
> Yes, I did look into igt_kselftest() and did notice the use of "all-tests",
> but for me that's not a documentation of an expected behavior, only a not
> quite fortunate implementation detail, forced by a mix of IGT contraints on
> one hand and implementation specifics of kernel side of i915 selftests on the
> other.
No, it is not just that. The tests actually announce that at runtime.
So, if you run the test with --list, you'll see:
$ ./build/tests/drm_mm --list-subtests
all-tests
And this is what it is used to check for testplan documentation.
> When you call an IGT test with a subtest name specified then only that subtest
> is executed, no matter if that's a selftest or a userspace test.
>
> When you call a userspace IGT test with no subtest name (pattern) specified
> then all subtests are executed and their names displayed. But when you do the
> same for an IGT selftest then all selftests are executed as one subtest named
> "all-tests". Do you think that's intentional, not a result of some
> constraints which no longer apply for kunit tests? Why do you prefer to keep
> the old inconsistent behavior instead of implementing IGT kunit tests to
> behave consistently with userspace IGT tests?
We can use whatever other name, provided that the output of
--list-subtests will be identical to the dynamic subtest. If not,
build will fail when checking for documentation inconsistencies.
Regards,
Mauro
next prev parent reply other threads:[~2023-06-06 13:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 10:47 [igt-dev] [PATCH v5 i-g-t 0/8] Introduce KUnit Dominik Karol Piatkowski
2023-06-05 10:47 ` [igt-dev] [PATCH i-g-t 1/8] lib/igt_kmod: rename kselftest functions to ktest Dominik Karol Piatkowski
2023-06-05 10:55 ` Mauro Carvalho Chehab
2023-06-05 10:47 ` [igt-dev] [PATCH i-g-t 2/8] lib/igt_kmod.c: check if module is builtin before attempting to unload it Dominik Karol Piatkowski
2023-06-05 10:56 ` Mauro Carvalho Chehab
2023-06-05 10:47 ` [igt-dev] [PATCH i-g-t 3/8] lib/igt_kmod: add compatibility for KUnit Dominik Karol Piatkowski
2023-06-05 10:59 ` Mauro Carvalho Chehab
2023-06-05 10:47 ` [igt-dev] [PATCH i-g-t 4/8] tests: DRM selftests: switch to KUnit Dominik Karol Piatkowski
2023-06-05 11:00 ` Mauro Carvalho Chehab
2023-06-07 10:24 ` Janusz Krzysztofik
2023-06-07 12:45 ` Mauro Carvalho Chehab
2023-06-07 14:35 ` Janusz Krzysztofik
2023-06-07 14:39 ` Janusz Krzysztofik
2023-06-07 15:59 ` Mauro Carvalho Chehab
2023-06-07 17:40 ` Janusz Krzysztofik
2023-06-08 7:56 ` Mauro Carvalho Chehab
2023-06-05 10:47 ` [igt-dev] [PATCH i-g-t 5/8] Change logic of ktap parser to run on a thread Dominik Karol Piatkowski
2023-06-05 11:03 ` Mauro Carvalho Chehab
2023-06-05 10:47 ` [igt-dev] [PATCH i-g-t 6/8] lib/igt_kmod: place KUnit tests on a subtest Dominik Karol Piatkowski
2023-06-06 7:44 ` Janusz Krzysztofik
2023-06-06 8:21 ` Mauro Carvalho Chehab
2023-06-06 8:41 ` Janusz Krzysztofik
2023-06-06 9:18 ` Mauro Carvalho Chehab
2023-06-06 10:03 ` Janusz Krzysztofik
2023-06-06 13:57 ` Mauro Carvalho Chehab [this message]
2023-06-06 14:22 ` Janusz Krzysztofik
2023-06-07 8:10 ` Mauro Carvalho Chehab
2023-06-05 10:47 ` [igt-dev] [PATCH i-g-t 7/8] kunit tests: add an optional name for the selftests Dominik Karol Piatkowski
2023-06-05 10:47 ` [igt-dev] [PATCH i-g-t 8/8] lib/igt_kmod: fix nesting igt_fixture in igt_subtest Dominik Karol Piatkowski
2023-06-05 11:05 ` Mauro Carvalho Chehab
2023-06-06 7:42 ` Janusz Krzysztofik
2023-06-08 13:31 ` Mauro Carvalho Chehab
2023-06-05 12:12 ` [igt-dev] ✓ Fi.CI.BAT: success for Introduce KUnit (rev5) Patchwork
2023-06-06 7:46 ` [igt-dev] [PATCH v5 i-g-t 0/8] Introduce KUnit Janusz Krzysztofik
2023-06-06 7:54 ` Piatkowski, Dominik Karol
2023-06-06 8:18 ` Mauro Carvalho Chehab
2023-06-06 8:35 ` Piatkowski, Dominik Karol
2023-06-07 14:07 ` Janusz Krzysztofik
2023-06-06 9:42 ` [igt-dev] ✗ Fi.CI.IGT: failure for Introduce KUnit (rev5) Patchwork
2023-06-09 10:15 ` [igt-dev] [PATCH v5 i-g-t 0/8] Introduce KUnit Janusz Krzysztofik
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=20230606155727.032e0fa3@maurocar-mobl2 \
--to=mauro.chehab@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.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