redonkable
/
alistair23-linux
1
0
Fork 0
Code Releases Activity

ktest: Add default for ssh-user, build-target and target-image 

When a user runs ktest without an argument, or the argument given
is not a config file that exists, ktest will ask the user a few
questions to create a simple ktest config file.

A few of the questions should have a default value set, that if anything
it will make it easier for the user to know what is suppose to
be in that value.

These new values are:

  SSH_USER, BUILD_TARGET and TARGET_IMAGE

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
hifive-unleashed-5.1
Steven Rostedt 2011-11-21 20:12:04 -05:00 committed by Steven Rostedt
parent de5b6e3bf5
commit 600bbf0aa2
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
tools/testing/ktest/ktest.pl
View File

@ -22,7 +22,6 @@ my %default;
#default opts
$default{"NUM_TESTS"} = 1;
$default{"REBOOT_TYPE"} = "grub";
$default{"TEST_TYPE"} = "test";
$default{"BUILD_TYPE"} = "randconfig";
$default{"MAKE_CMD"} = "make";
@ -51,7 +50,14 @@ $default{"REBOOT"} = "ssh \$SSH_USER\@\$MACHINE reboot";
$default{"STOP_AFTER_SUCCESS"} = 10;
$default{"STOP_AFTER_FAILURE"} = 60;
$default{"STOP_TEST_AFTER"} = 600;
# required, and we will ask users if they don't have them but we keep the default
# value something that is common.
$default{"REBOOT_TYPE"} = "grub";
$default{"LOCALVERSION"} = "-test";
$default{"SSH_USER"} = "root";
$default{"BUILD_TARGET"} = "arch/x86/boot/bzImage";
$default{"TARGET_IMAGE"} = "/boot/vmlinuz-test";
my $ktest_config;
my $version;