On 17/12/2025 16:00, Mark Brown wrote:
On Wed, Dec 17, 2025 at 03:59:02PM +0200, Péter Ujfalusi wrote:
On 17/12/2025 15:56, Mark Brown wrote:
What do you mean by "kunit test setup" - that's just a self contained Python script that drives everything, it has minimal Python requirements.
I'm holding it wrong I'm sure:
[15:35:21] Configuring KUnit Kernel ... [15:35:21] Building KUnit Kernel ... Populating config with: $ make ARCH=um O=.kunit olddefconfig
What did you actually run there? Did you somehow have an existing .config that it was picking up with everything turned off?
git clean -xdf make mrproper
./tools/testing/kunit/kunit.py run --alltests [16:09:25] Configuring KUnit Kernel ... Generating .config ... Populating config with: $ make ARCH=um O=.kunit olddefconfig [16:09:30] Building KUnit Kernel ... Populating config with: $ make ARCH=um O=.kunit olddefconfig Building with: $ make all compile_commands.json scripts_gdb ARCH=um O=.kunit --jobs=14 [16:12:52] Starting KUnit Kernel (1/1)... [16:12:52] ============================================================ Running tests with: $ .kunit/linux kunit.enable=1 mem=1G console=tty kunit_shutdown=halt [16:12:52] [ERROR] Test: <missing>: Could not find any KTAP output. Did any KUnit tests run? [16:12:52] ============================================================ [16:12:52] Testing complete. Ran 0 tests: errors: 1 [16:12:52] Elapsed time: 206.260s total, 4.835s configuring, 201.418s building, 0.007s running
well, this is for the cold and dark winter days.. ;)