linux-toradex.git/tools/testing/ktest, branch master

ktest: Accept quoted bad term in git bisect output

2026-10-20T19:52:01+00:00

Git commit 0c0f93e7fa64 ("bisect: print bisect terms in single quotes")
changed the completion message to put single quotes around the bisect term.
run_git_bisect() only recognizes "is the first bad commit", so it misses
completion and continues the bisect loop with newer Git.

Accept both quoted and unquoted forms to retain compatibility with older
Git versions.

Link: https://git.kernel.org/pub/scm/git/git.git/commit/?id=0c0f93e7fa645c1058226a9bfde9e2b4441edf96
Assisted-by: LLM
Signed-off-by: Ricardo B. Marlière (SUSE) 
Signed-off-by: Steven Rostedt

ktest.pl: Add total test run time to output

2026-10-20T18:18:37+00:00

It can be interesting to know what the total time of all the tests took.
Instead of just seeing the time for each individual test, at the end of
the test (even on failure) show the total time the test took to complete.
This can also help identify if something has changed in the setup that
should be investigated if the times suddenly increase drastically.

Link: https://patch.msgid.link/20261020103338.4be97a72@gandalf.local.home
Signed-off-by: Steven Rostedt

ktest: Sort config keys before writing config files

2026-10-20T18:18:37+00:00

apply_min_config(), save_config(), and make_min_config() write CONFIG_*
lines by iterating "keys %hash" with no sort. Perl randomizes hash
iteration order per process by default, so the line order of the resulting
config files is not reproducible across otherwise identical invocations.

When two of those lines are mutually exclusive members of the same Kconfig
"choice", this can change which one "make olddefconfig" keeps,
nondeterministically, from run to run. Observed with
CONFIG_DEBUG_INFO_DWARF5 vs CONFIG_DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT: five
consecutive "-C" builds from identical ADD_CONFIG/MIN_CONFIG inputs
alternated between the two, which is enough to force a near-complete
rebuild each time since CONFIG_DEBUG_INFO_* affects every object's compile
flags.

Sort the keys before writing so the same inputs always produce the same
config output.

Link: https://patch.msgid.link/20261014-ktest-kconfig-perl-hash-v1-1-66201a2dee82@marliere.net
Signed-off-by: Ricardo B. Marlière (SUSE) 
Signed-off-by: Steven Rostedt

ktest: Add logfile to failure directory

2026-04-20T19:23:13+00:00

The logfile contains a lot of useful information about the tests being
run. Add it to the stored failure directory when the test fails.

Cc: John 'Warthog9' Hawley 
Link: https://patch.msgid.link/20260420142315.7bbc3624@fedora
Signed-off-by: Steven Rostedt

ktest: Fix the month in the name of the failure directory

2026-04-20T19:23:13+00:00

The Perl localtime() function returns the month starting at 0 not 1. This
caused the date produced to create the directory for saving files of a
failed run to have the month off by one.

  machine-test-useconfig-fail-20260314073628

The above happened in April, not March. The correct name should have been:

  machine-test-useconfig-fail-20260414073628

This was somewhat confusing.

Cc: stable@vger.kernel.org
Cc: John 'Warthog9' Hawley 
Link: https://patch.msgid.link/20260420142426.33ad0293@fedora
Fixes: 7faafbd69639b ("ktest: Add open and close console and start stop monitor")
Signed-off-by: Steven Rostedt

ktest: Store failure logs also in fatal paths

2026-03-18T20:00:54+00:00

STORE_FAILURES was only saved from fail(), so paths that reached dodie()
could exit without preserving failure logs.

That includes fatal hook paths such as:

  POST_BUILD_DIE = 1

and ordinary failures when:

  DIE_ON_FAILURE = 1

Call save_logs("fail", ...) from dodie() too so fatal failures keep the
same STORE_FAILURES artifacts as non-fatal fail() paths.

Cc: John Hawley 
Link: https://patch.msgid.link/20260318-ktest-fixes-v1-1-9dd94d46d84c@suse.com
Signed-off-by: Ricardo B. Marlière 
Signed-off-by: Steven Rostedt

ktest: Add a --dry-run mode

2026-03-09T15:03:00+00:00

When working on a ktest configuration, it is often useful to inspect the
final option values after includes, defaults, per-test overrides, and
variable expansion have been applied, without actually starting a test run.

Add a --dry-run option that reads the configuration, prints the test
preamble using resolved option values, and exits before opening LOG_FILE or
executing any test logic.

This is useful for debugging ktest configurations and for scripts that need
to validate the final resolved settings without triggering side effects.

Cc: John Hawley 
Cc: Andrea Righi 
Cc: Marcos Paulo de Souza 
Cc: Matthieu Baerts 
Cc: Fernando Fernandez Mancera 
Cc: Pedro Falcato 
Link: https://patch.msgid.link/20260307-ktest-fixes-v1-9-565d412f4925@suse.com
Signed-off-by: Ricardo B. Marlière 
Signed-off-by: Steven Rostedt

ktest: Run POST_KTEST hooks on failure and cancellation

2026-03-09T15:02:18+00:00

PRE_KTEST can be useful for setting up the environment and POST_KTEST to
tear it down, however POST_KTEST only runs on the normal end-of-run path.
It is skipped when ktest exits through dodie() or cancel_test(). Final
cleanup hooks are skipped.

Factor the final hook execution into run_post_ktest(), call it from the
normal exit path and from the early exit paths, and guard it so the hook
runs at most once.

Cc: John Hawley 
Cc: Andrea Righi 
Cc: Marcos Paulo de Souza 
Cc: Matthieu Baerts 
Cc: Fernando Fernandez Mancera 
Cc: Pedro Falcato 
Link: https://patch.msgid.link/20260307-ktest-fixes-v1-8-565d412f4925@suse.com
Fixes: 921ed4c7208e ("ktest: Add PRE/POST_KTEST and TEST options")
Signed-off-by: Ricardo B. Marlière 
Signed-off-by: Steven Rostedt

ktest: Add PRE_KTEST_DIE for PRE_KTEST failures

2026-03-09T14:32:08+00:00

PRE_KTEST runs before the first test, but its return status is currently
ignored. A failing setup hook can leave the rest of the run executing in a
partially initialized environment.

Add PRE_KTEST_DIE so PRE_KTEST can fail the run in the same way
PRE_BUILD_DIE and PRE_TEST_DIE already can. Keep the default behavior
unchanged when the new option is not set.

Cc: John Hawley 
Cc: Andrea Righi 
Cc: Marcos Paulo de Souza 
Cc: Matthieu Baerts 
Cc: Fernando Fernandez Mancera 
Cc: Pedro Falcato 
Link: https://patch.msgid.link/20260307-ktest-fixes-v1-7-565d412f4925@suse.com
Signed-off-by: Ricardo B. Marlière 
Signed-off-by: Steven Rostedt

ktest: Stop dropping console output during power-cycle reboot

2026-03-09T14:32:07+00:00

The POWER_CYCLE fallback added to reboot() flushes monitor output at the
wrong time. In the untimed reboot path, flushing immediately after
start_monitor() can consume the first output from the new boot before
monitor() begins reading it. In the timed path, flushing after POWER_CYCLE
can eat the "Linux version" banner or REBOOT_SUCCESS_LINE from the new
kernel.

That makes ktest miss the boot it is waiting for and can trigger an
unnecessary second power cycle.

Start the monitor before POWER_CYCLE so the reference counting stays
balanced, but only flush when reboot() was asked to wait for a timed
reboot. Perform that flush before issuing POWER_CYCLE so it drains stale
output from the old kernel instead of consuming the next boot.

Cc: John Hawley 
Cc: Andrea Righi 
Cc: Marcos Paulo de Souza 
Cc: Matthieu Baerts 
Cc: Fernando Fernandez Mancera 
Cc: Pedro Falcato 
Link: https://patch.msgid.link/20260307-ktest-fixes-v1-6-565d412f4925@suse.com
Signed-off-by: Ricardo B. Marlière 
Signed-off-by: Steven Rostedt