On Sun, Aug 28, 2022 at 09:09:20PM -0300, Isabella Basso wrote:
As the DRM selftests are now using KUnit [1], update IGT tests as well.
[1] - https://lore.kernel.org/all/20220708203052.236290-1-maira.canal@usp.br/
Signed-off-by: Isabella Basso isabbasso@riseup.net
tests/drm_buddy.c | 7 ++++--- tests/drm_mm.c | 7 ++++--- tests/kms_selftest.c | 12 +++++++++--- 3 files changed, 17 insertions(+), 9 deletions(-)
diff --git a/tests/drm_buddy.c b/tests/drm_buddy.c index 06876e0c..74c06dce 100644 --- a/tests/drm_buddy.c +++ b/tests/drm_buddy.c @@ -6,9 +6,10 @@ #include "igt.h" #include "igt_kmod.h" -IGT_TEST_DESCRIPTION("Basic sanity check of DRM's buddy allocator (struct drm_buddy)"); +IGT_TEST_DESCRIPTION("Basic sanity check of DRM's buddy allocator (struct \
drm_buddy) using KUnit");-igt_main +igt_simple_main {
- igt_kselftests("test-drm_buddy", NULL, NULL, NULL);
- igt_kunit("drm_buddy_test", NULL);
}
With kselftests we had the ability to only run a specified set of tests, and with or without selection, we had sub-results for each through dynamic subtests. Does kunit have that possibility? I mean I know kunit itself does but what about igt_kunit()?
Orthogonal to that question, drm_mm and test-drm_modeset are _now_ using kunit but in LTS kernels they're not, and we'd like to be able to keep testing those. That means having both launchers here and just letting the "incorrect" one produce a 'skip'.