[PATCH 0/9] tools/testing/ktest: Fixes and a new --dry-run

Ricardo B. Marlière posted 9 patches 1 month ago
tools/testing/ktest/ktest.pl    | 158 +++++++++++++++++++++++++++++-----------
tools/testing/ktest/sample.conf |   6 ++
2 files changed, 122 insertions(+), 42 deletions(-)
[PATCH 0/9] tools/testing/ktest: Fixes and a new --dry-run
Posted by Ricardo B. Marlière 1 month ago
Hi Steven,

Please consider the following ktest patches.

They fix a few edge cases that I found while using ktest with a small
virtme-ng-based harness [1], and the last two add small features:
PRE_KTEST_DIE and a new --dry-run 

Thanks!
-	Ricardo.

[1]: https://github.com/rbmarliere/k-lab

Assisted-by: codex 5.3
Signed-off-by: Ricardo B. Marlière <rbm@suse.com>
---
Ricardo B. Marlière (9):
      ktest: Avoid undef warning when WARNINGS_FILE is unset
      ktest: Resolve LOG_FILE in test option context
      ktest: Treat undefined self-reference as empty
      ktest: Honor empty per-test option overrides
      ktest: Run commands through list-form shell open
      ktest: Stop dropping console output during power-cycle reboot
      ktest: Add PRE_KTEST_DIE for PRE_KTEST failures
      ktest: Run POST_KTEST hooks on failure and cancellation
      ktest: Add a --dry-run mode

 tools/testing/ktest/ktest.pl    | 158 +++++++++++++++++++++++++++++-----------
 tools/testing/ktest/sample.conf |   6 ++
 2 files changed, 122 insertions(+), 42 deletions(-)
---
base-commit: 4ae12d8bd9a830799db335ee661d6cbc6597f838
change-id: 20260307-ktest-fixes-0ff398d65521

Best regards,
-- 
Ricardo B. Marlière <rbm@suse.com>

Re: [PATCH 0/9] tools/testing/ktest: Fixes and a new --dry-run
Posted by Steven Rostedt 1 month ago
On Sat, 07 Mar 2026 19:07:55 -0300
Ricardo B. Marlière <rbm@suse.com> wrote:

> Hi Steven,

Hi Ricardo,

> 
> Please consider the following ktest patches.
> 
> They fix a few edge cases that I found while using ktest with a small
> virtme-ng-based harness [1], and the last two add small features:
> PRE_KTEST_DIE and a new --dry-run 

Thanks, I'll do a review and apply it to my local tree. As I use ktest
daily, I always run updates locally for a while before pushing it up, as my
normal day to day usage can find subtle bugs.

-- Steve