Lines Matching full:will
5 # ktest.pl is run from. By default, ktest.pl will look for a file
26 # Each TEST_START label will set up a new test. If you want to
29 # to iterate. If the ITERATE is left off, the test will only
61 # The above will run the first test with MIN_CONFIG set to
62 # /home/test/config-test-1. Then 10 tests will be executed
73 # The above will ignore the first MIN_CONFIG. If you want to
78 # ktest will fail to execute, and no tests will run.
89 # been defined previously. It will only override options that
91 # in a non override section will still error. The same option
103 # The above will process the DEFAULTS section if the config
105 # otherwise if it evaluates to zero, it will act the same
135 # The if statement may also have comparisons that will and for
175 # The INCLUDE keyword may be used in DEFAULT sections. This will
178 # statements. Config variables will be passed to these files and changes
179 # to config variables will be seen by top level config files. Including
182 # TEST_START sections will have that section ended at the end of
211 # where each instance will override the previous instance.
252 # use the ${X} convention. Simple $X will not work.
254 # If the config variable does not exist, the ${X} will not
260 # the MAKE_CMD option will be evaluated by the shell when
278 # The option will be used per test case. Thus:
289 # For both test cases, MACHINE will be evaluated at the time
290 # of the test case. The first test will run ssh root@box1
291 # and the second will run ssh root@box2.
298 # The machine hostname that you will test
308 # The directory that the objects will be built
337 # ktest.pl will create a child process to monitor the console.
338 # When the console is finished, ktest will kill the child process
360 # Note, ktest.pl will not update the grub menu.lst, you need to
361 # manually add an option for the test. ktest.pl will search
427 # ktest.pl will do the substitution for MAIL_PATH, MAILER, MAILTO at the time
429 # then the substitutions will occur at the time the config file is read.
447 # as a LOG_FILE is defined, then the log of the failing test will
451 # much of the log is sent, set MAIL_MAX_SIZE. This will be the
454 # last 100 thousand bytes of the log file will be included in
460 # will be default and the test will run once.
476 # section will be ignored.
483 # or an option in the first test case. All other test cases will
485 # set, then the first test will take precedence.
493 # set this option, then the last test case that set it will take
538 # The environment variable KERNEL_VERSION will be set to the
545 # it. The environment variable KERNEL_VERSION will be set to the
588 # fix a unrelated bug to perform a patchcheck test. This will apply the
619 # If you specify grub, it will assume grub version 1
620 # and will search in /boot/grub/menu.lst for the title $GRUB_MENU
635 # The test will not modify that file.
654 # This option holds a command that will execute before needing
685 # localyesconfig again. The CONFIG_MIN generated like this will
704 # This option points to the file containing config options that will be prepended
707 # Note, config options in MIN_CONFIG will override these options.
739 # a new test kernel to it. Otherwise ktest.pl will wait till
764 # Stop testing if a build fails. If set, the script will end if
765 # a failure is detected, otherwise it will save off the .config,
775 # set, DIE_ON_FAILURE=0 will not save off the .config, dmesg and
781 # set, the .config, dmesg and bootlog will not be saved if a
833 # ever finishing, this will cause ktest to get stuck. This
834 # option is the max time ktest will wait for the monitor (console)
890 # WARNINGS_FILE is set, then that file will be read, and if the
891 # build detects a warning, it will examine this file and if the
892 # warning does not exist in it, it will fail the build.
895 # then any warning will fail the build.
915 # option will override the SCP_TO_TARGET for installation.
940 # in the config file is not used, ktest will warn about it and ask
950 # traces, ktest.pl will detect these and fail a boot or test run
951 # due to warnings. By setting this option, ktest will ignore
952 # call traces, and will not fail a test if the kernel produces
970 # specify this for the first run, that branch will be used for
984 # will checkout the PATCHCHECK_START commit.
986 # The option BUILD_TYPE will be ignored.
988 # The MIN_CONFIG will be used for all builds of the patchcheck. The build type
997 # PATCHCHECK_CHERRY if set to non zero, then git cherry will be
1002 # Then the changes found will be tested.
1010 # Note, the build test will look for warnings, if a warning occurred
1011 # in a file that a commit touches, the build will fail, unless
1018 # If BUILD_NOCLEAN is set, then make mrproper will not be run on
1038 # The MIN_CONFIG will be used for all builds of the bisect. The build type
1041 # The option BUILD_TYPE will be ignored.
1056 # fail. Then the test ends. The state of the BUILD_DIR will be
1067 # And running the test again. The test will perform the initial
1069 # then it will run git bisect replay on this file, before
1077 # will checkout that commit after doing the initial git bisect start,
1083 # If BISECT_TYPE is set to test but the build fails, ktest will
1087 # when something other than the BISECT_TYPE fails, ktest.pl will
1097 # Will run the bisect with "git bisect start -- arch/x86 kernel/time"
1105 # With BISECT_REVERSE = 1, The test will consider failures as
1112 # Doing a BISECT_MANUAL will have the test wait for you to
1115 # but ktest will rebuild and install the kernel for you.
1120 # BISECT_CHECK to 1 will start the bisect by first checking
1121 # out BISECT_BAD and makes sure it fails, then it will check
1134 # will stop trying and mark the current SHA1 as bad.
1140 # You can set BISECT_TRIES to zero, and all tests will be considered
1175 # and define BISECT_RET_DEFAULT, all bisects results will do
1194 # The TEST_TYPE config_bisect will bisect the bad config looking for
1200 # will use the MIN_CONFIG, and if that's not specified, it will use
1208 # It will set half of the good configs within the bad config (note,
1210 # in the good config that is off, will be turned off in the bad
1215 # process until there's only one config left and it will report that
1229 # The option BUILD_TYPE will be ignored.
1238 # If BISECT_MANUAL is set, it will pause between iterations.
1240 # If you set it to build, it will run the bisect and you can
1241 # control what happens in between iterations. It will ask you if
1248 # It will build a config with "make defconfig"
1254 # and the test will not return a result.
1260 # By default, it will look for:
1262 # If it does not find it there, it will look for:
1264 # If it does not find it there, it will look for:
1266 # Setting CONFIG_BISECT_EXEC will override where it looks.
1285 # will give you less of a chance that one of your set configurations
1286 # will make the bug go away. This will give you a better chance to
1302 # config, that config will be checked first. By checking the
1307 # the CONFIG_USB will be tested before the device. If CONFIG_USB is
1309 # it, will be disabled and removed from the current min_config.
1311 # OUTPUT_MIN_CONFIG is the path and filename of the file that will
1316 # If this file exists, you will be prompted if you want to use it
1330 # it left off. New configs that it finds will be written to this file
1331 # and will not be tested again in later runs.
1334 # MIN_CONFIG_TYPE can be either 'boot' or 'test'. With 'boot' it will
1337 # config will not only boot the target, but also make sure that the
1345 # If it is not defined, it will prompt you to pick which config
1365 # The test "make_warnings_file" will let you create a new warnings
1370 # A BUILD_TYPE of nobuild will fail this test.
1372 # The test will do the build and scan for all warnings. Any warning
1373 # it discovers will be saved in the WARNINGS_FILE (required) option.
1377 # That way, all warnings will be captured.