testing/ktest/sample.conf

21 # Each TEST_START label will set up a new test. If you want to
24 # to iterate. If the ITERATE is left off, the test will only
56 # The above will run the first test with MIN_CONFIG set to
57 # /home/test/config-test-1. Then 10 tests will be executed
68 # The above will ignore the first MIN_CONFIG. If you want to
73 # ktest will fail to execute, and no tests will run.
84 # been defined previously. It will only override options that
86 # in a non override section will still error. The same option
98 # The above will process the DEFAULTS section if the config
100 # otherwise if it evaluates to zero, it will act the same
130 # The if statement may also have comparisons that will and for
170 # The INCLUDE keyword may be used in DEFAULT sections. This will
173 # statements. Config variables will be passed to these files and changes
174 # to config variables will be seen by top level config files. Including
177 # TEST_START sections will have that section ended at the end of
206 # where each instance will override the previous instance.
247 # use the ${X} convention. Simple $X will not work.
249 # If the config variable does not exist, the ${X} will not
255 # the MAKE_CMD option will be evaluated by the shell when
273 # The option will be used per test case. Thus:
284 # For both test cases, MACHINE will be evaluated at the time
285 # of the test case. The first test will run ssh root@box1
286 # and the second will run ssh root@box2.
293 # The machine hostname that you will test
303 # The directory that the objects will be built
338 # Note, ktest.pl will not update the grub menu.lst, you need to
339 # manually add an option for the test. ktest.pl will search
358 # will be default and the test will run once.
374 # section will be ignored.
412 # it. The environment variable KERNEL_VERSION will be set to the
433 # fix a unrelated bug to perform a patchcheck test. This will apply the
464 # If you specify grub, it will assume grub version 1
465 # and will search in /boot/grub/menu.lst for the title $GRUB_MENU
471 # The test will not modify that file.
490 # This option holds a command that will execute before needing
521 # localyesconfig again. The CONFIG_MIN generated like this will
540 # This option points to the file containing config options that will be prepended
543 # Note, config options in MIN_CONFIG will override these options.
575 # a new test kernel to it. Otherwise ktest.pl will wait till
600 # Stop testing if a build fails. If set, the script will end if
601 # a failure is detected, otherwise it will save off the .config,
611 # set, DIE_ON_FAILURE=0 will not save off the .config, dmesg and
617 # set, the .config, dmesg and bootlog will not be saved if a
735 # in the config file is not used, ktest will warn about it and ask
745 # traces, ktest.pl will detect these and fail a boot or test run
746 # due to warnings. By setting this option, ktest will ignore
747 # call traces, and will not fail a test if the kernel produces
765 #  specify this for the first run, that branch will be used for
779 #  will checkout the PATCHCHECK_START commit.
781 #  The option BUILD_TYPE will be ignored.
783 #  The MIN_CONFIG will be used for all builds of the patchcheck. The build type
795 #   Note, the build test will look for warnings, if a warning occurred
796 #     in a file that a commit touches, the build will fail, unless
803 #   If BUILD_NOCLEAN is set, then make mrproper will not be run on
823 #  The MIN_CONFIG will be used for all builds of the bisect. The build type
826 #  The option BUILD_TYPE will be ignored.
841 #   fail. Then the test ends. The state of the BUILD_DIR will be
852 #   And running the test again. The test will perform the initial
854 #    then it will run git bisect replay on this file, before
862 #   will checkout that commit after doing the initial git bisect start,
868 #   If BISECT_TYPE is set to test but the build fails, ktest will
872 #   when something other than the BISECT_TYPE fails, ktest.pl will
882 #   Will run the bisect with "git bisect start -- arch/x86 kernel/time"
890 #   With BISECT_REVERSE = 1, The test will consider failures as
897 #   Doing a BISECT_MANUAL will have the test wait for you to
900 #   but ktest will rebuild and install the kernel for you.
905 #   BISECT_CHECK to 1 will start the bisect by first checking
906 #   out BISECT_BAD and makes sure it fails, then it will check
946 #   and define BISECT_RET_DEFAULT, all bisects results will do
965 #  The TEST_TYPE config_bisect will bisect the bad config looking for
980 #   appears will be added to the configs to test.
997 #   will be enabled for all builds (they will be enabled, but not be part
1001 #   the config file are removed from the test. These configs will not
1014 #  The option BUILD_TYPE will be ignored.
1023 #  If BISECT_MANUAL is set, it will pause between iterations.
1025 #  If you set it to build, it will run the bisect and you can
1026 #  control what happens in between iterations. It will ask you if
1051 #  will give you less of a chance that one of your set configurations
1052 #  will make the bug go away. This will give you a better chance to
1068 #  config, that config will be checked first. By checking the
1073 #  the CONFIG_USB will be tested before the device. If CONFIG_USB is
1075 #  it, will be disabled and removed from the current min_config.
1077 #  OUTPUT_MIN_CONFIG is the path and filename of the file that will
1082 #   If this file exists, you will be prompted if you want to use it
1096 #   it left off. New configs that it finds will be written to this file
1097 #   and will not be tested again in later runs.