On Fri, Jul 22, 2022 at 08:04:51AM -0300, Maíra Canal wrote: > On 7/22/22 07:35, Matthew Auld wrote: > > On Fri, 8 Jul 2022 at 21:32, Maíra Canal <maira.canal@xxxxxx> wrote: > >> > >> From: Arthur Grillo <arthur.grillo@xxxxxx> > >> > >> Considering the current adoption of the KUnit framework, convert the > >> DRM mm selftest to the KUnit API. > > > > Is there a plan to convert the corresponding selftest IGT that was > > responsible for running this (also drm_buddy) to somehow work with > > kunit? Previously these IGTs were always triggered as part of > > intel-gfx CI, but it looks like they are no longer run[1]. > > > > [1] https://gitlab.freedesktop.org/drm/intel/-/issues/6433 > > Hi Matthew, > > Isabella sent a while ago a patch to IGT adding KUnit compatibility to > IGT [1], but there wasn't any feedback on the patch. I believe that soon > she will resend the series in order to make all KUnit DRM tests run on IGT. > > Any feedback on the patch is welcomed so that we can fix this issue as > soon as possible. > > [1] https://patchwork.freedesktop.org/patch/489985/ > > Best Regards, > - Maíra Canal Hi. Instead of going back to using IGT for *unit* tests, it would be a better idea to adjust the CI to just run the tests once at "build" time (just like e.g. checkpatch). We would then stop executing the same test multiple times on different machines (note that both DRM selftests and i915 "mock" selftests are pure unit tests - in other words, they don't need the hardware to be present), which would save some (small) amount of machine-time that can be utilized to do something that actually needs the hardware. Plus there's no need to maintain the kunit-runner in IGT. Note - we're currently going to lose "DMESG-WARN" detection if we go this route, but this is something that can be improved on the kunit-side. -Michał
