Re: [PATCH v2 3/4] kfence: test: use new suite_{init/exit} support, add .kunitconfig

[Brendan Higgins]

On Fri, Apr 29, 2022 at 2:13 PM Daniel Latypov <dlatypov@xxxxxxxxxx> wrote:
>
> Currently, the kfence test suite could not run via "normal" means since
> KUnit didn't support per-suite setup/teardown. So it manually called
> internal kunit functions to run itself.
> This has some downsides, like missing TAP headers => can't use kunit.py
> to run or even parse the test results (w/o tweaks).
>
> Use the newly added support and convert it over, adding a .kunitconfig
> so it's even easier to run from kunit.py.
>
> People can now run the test via
> $ ./tools/testing/kunit/kunit.py run --kunitconfig=mm/kfence --arch=x86_64
> ...
> [11:02:32] Testing complete. Passed: 23, Failed: 0, Crashed: 0, Skipped: 2, Errors: 0
> [11:02:32] Elapsed time: 43.562s total, 0.003s configuring, 9.268s building, 34.281s running
>
> Cc: kasan-dev@xxxxxxxxxxxxxxxx
> Signed-off-by: Daniel Latypov <dlatypov@xxxxxxxxxx>
> Tested-by: David Gow <davidgow@xxxxxxxxxx>
> Reviewed-by: Marco Elver <elver@xxxxxxxxxx>

Reviewed-by: Brendan Higgins <brendanhiggins@xxxxxxxxxx>