On 1/6/26 18:59, David Gow wrote:
From: Thomas Weißschuh thomas.weissschuh@linutronix.de
If no kunitconfig_paths are passed to LinuxSourceTree() it falls back to DEFAULT_KUNITCONFIG_PATH. This resolution only works when the current working directory is the root of the source tree. This works by chance when running the full testsuite through the default unittest runner, as some tests will change the current working directory as a side-effect of 'kunit.main()'. When running a single testcase or using pytest, which resets the working directory for each test, this assumption breaks.
Explicitly specify an empty kunitconfig for the affected tests.
Signed-off-by: Thomas Weißschuh thomas.weissschuh@linutronix.de Reviewed-by: David Gow davidgow@google.com Signed-off-by: David Gow davidgow@google.com
Changes since v1: https://lore.kernel.org/linux-kselftest/20251230-kunit-pytest-v1-2-e2dae0dae...
- No-op rebase on top of kselftest/kunit
Thank you.
Applied to linux kselftest kunit repo for Linux 6.20-rc1
thanks, -- Shuah