[PATCH] ktest: force $buildonly = 1 for 'make_warnings_file' test type

From: Ricardo B. Marliere
Date: Tue Mar 05 2024 - 12:03:09 EST


The test type "make_warnings_file" should have no mandatory configuration
parameters other than the ones required by the "build" test type, because
its purpose is to create a file with build warnings that may or may not be
used by other subsequent tests. Currently, the only way to use it as a
stand-alone test is by setting POWER_CYCLE, CONSOLE, SSH_USER,
BUILD_TARGET, TARGET_IMAGE, REBOOT_TYPE and GRUB_MENU.

Signed-off-by: Ricardo B. Marliere <ricardo@xxxxxxxxxxxx>
---
tools/testing/ktest/ktest.pl | 1 +
1 file changed, 1 insertion(+)

diff --git a/tools/testing/ktest/ktest.pl b/tools/testing/ktest/ktest.pl
index 829f5bdfd2e4..ab4bf87ba991 100755
--- a/tools/testing/ktest/ktest.pl
+++ b/tools/testing/ktest/ktest.pl
@@ -843,6 +843,7 @@ sub set_value {
if ($lvalue =~ /^(TEST|BISECT|CONFIG_BISECT)_TYPE(\[.*\])?$/ &&
$prvalue !~ /^(config_|)bisect$/ &&
$prvalue !~ /^build$/ &&
+ $prvalue !~ /^make_warnings_file/ &&
$buildonly) {

# Note if a test is something other than build, then we

---
base-commit: 7e90b5c295ec1e47c8ad865429f046970c549a66
change-id: 20240305-ktest-9e4452112c93

Best regards,
--
Ricardo B. Marliere <ricardo@xxxxxxxxxxxx>