On Fri, Apr 19, 2024 at 04:38:01PM -0700, Guenter Roeck wrote: > On Fri, Apr 19, 2024 at 03:33:49PM -0700, Guenter Roeck wrote: > > Hi, > > > > On Tue, Mar 19, 2024 at 11:48:57AM +0100, Mickaël Salaün wrote: > > > Add a test case to check NULL pointer dereference and make sure it would > > > result as a failed test. > > > > > > The full kunit_fault test suite is marked as skipped when run on UML > > > because it would result to a kernel panic. > > > > > > Tested with: > > > ./tools/testing/kunit/kunit.py run --arch x86_64 kunit_fault > > > ./tools/testing/kunit/kunit.py run --arch arm64 \ > > > --cross_compile=aarch64-linux-gnu- kunit_fault > > > > > > > What is the rationale for adding those tests unconditionally whenever > > CONFIG_KUNIT_TEST is enabled ? This completely messes up my test system > > because it concludes that it is pointless to continue testing > > after the "Unable to handle kernel NULL pointer dereference" backtrace. > > At the same time, it is all or nothing, meaning I can not disable > > it but still run other kunit tests. > > CONFIG_KUNIT_TEST is to test KUnit itself. Why does this messes up your test system, and what is your test system? Is it related to the kernel warning and then the message you previously sent? https://lore.kernel.org/r/fd604ae0-5630-4745-acf2-1e51c69cf0c0@xxxxxxxxxxxx It seems David has a solution to suppress such warning. > > Oh, never mind. I just disabled CONFIG_KUNIT_TEST in my test bed > to "solve" the problem. I'll take that as one of those "unintended > consequences" items: Instead of more tests, there are fewer. > > Guenter >
