Re: [PATCH] kunit: tool: Terminate kernel under test on SIGINT

[Andy Shevchenko <andriy.shevchenko@intel.com>]

On Sat, Feb 28, 2026 at 06:07:22PM +0800, David Gow wrote:
> kunit.py will attempt to catch SIGINT / ^C in order to ensure the TTY isn't
> messed up, but never actually attempts to terminate the running kernel (be
> it UML or QEMU). This can lead to a bit of frustration if the kernel has
> crashed or hung.
> 
> Terminate the kernel process in the signal handler, if it's running. This
> requires plumbing through the process handle in a few more places (and
> having some checks to see if the kernel is still running in places where it
> may have already been killed).

I killed my branch with those experiments already. But it's really appreciated
to see this going to the right direction.

> Reported-by: Andy Shevchenko <andriy.shevchenko@intel.com>

In any case, god bless `git reflog`, I got it still from there and hence

Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
Tested-by: Andy Shevchenko <andriy.shevchenko@intel.com>

(Have to applied the other mentioned patch first)

Now

  ^CERROR:root:Build interruption occurred. Cleaning console.
  [11:36:29] [ERROR] Test: <missing>: Could not find any KTAP output. Did any KUnit tests run?
  [11:36:29] ============================================================
  [11:36:29] Testing complete. Ran 0 tests: errors: 1
  [11:36:29] Elapsed time: 33.615s total, 0.001s configuring, 5.122s building, 28.492s running

-- 
With Best Regards,
Andy Shevchenko