Lines Matching +full:skip +full:- +full:config

2 # Config file for ktest.pl
7 # the name of your config file as the first argument of ktest.pl.
34 # You can skip a test by adding SKIP (before or after the ITERATE
37 # TEST_START SKIP
39 # TEST_START SKIP ITERATE 10
41 # TEST_START ITERATE 10 SKIP
43 # The SKIP label causes the options and the test itself to be ignored.
44 # This is useful to set up several different tests in one config file, and
54 # MIN_CONFIG = /home/test/config-test1
57 # MIN_CONFIG = /home/test/config-default
62 # /home/test/config-test-1. Then 10 tests will be executed
63 # with MIN_CONFIG with /home/test/config-default.
65 # You can also disable defaults with the SKIP option
67 # DEFAULTS SKIP
68 # MIN_CONFIG = /home/test/config-use-sometimes
71 # MIN_CONFIG = /home/test/config-most-times
74 # use the first MIN_CONFIG, remove the SKIP from the first
99 # integer, and can use the config variables (explained below).
103 # The above will process the DEFAULTS section if the config
106 # as if the SKIP keyword was used.
112 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-network
116 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-normal
124 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-network
127 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-tests
130 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-cpu
133 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-network
141 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-32
143 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-64
146 # It returns true if the given config variable or option has been defined
176 # read another config file and process that file as well. The included
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
186 # Unlike other files referenced in this config, the file path does not need
188 # that the current config file was located in is used. If no config by the
203 #### Config variables ####
205 # This config file can also contain "config variables".
209 # The difference between ktest options and config variables
210 # is that config variables can be used multiple times,
212 # And that they only live at time of processing this config.
214 # The advantage to config variables are that they can be used
215 # by any option or any other config variables to define thing
247 # Note, the config variables are evaluated immediately, thus
251 # As shown in the example, to evaluate a config variable, you
254 # If the config variable does not exist, the ${X} will not
259 # If PATH is not a config variable, then the ${PATH} in
273 # Options that are defined in the config file may also be used
275 # use (except that config variables are evaluated at config
280 # just like you can config variables.
325 #TARGET_IMAGE = /boot/vmlinuz-test
330 #POWER_CYCLE = wget --no-proxy -O /dev/null -q  --auth-no-challenge 'http://admin:admin@power/outle…
339 #CONSOLE = nc -d localhost 3001
353 #LOCALVERSION = -test
375 # kernel vmlinuz-test
403 # test kernel in the syslinux config file.
405 #SYSLINUX_LABEL = "test-kernel"
414 #### Optional Config Options (all have defaults) ####
432 #  MAIL_COMMAND = echo \'Subject: $SUBJECT\n\n$MESSAGE\' | $MAIL_PATH/$MAILER -t $MAILTO
434 #  MAIL_COMMAND = "$MAIL_PATH/$MAILER -s \'$SUBJECT\' $MAILTO <<< \'$MESSAGE\'
437 #    then the substitutions will occur at the time the config file is read.
438 #    But note, MAIL_PATH and MAILER require being set by the config file if
440 #MAIL_COMMAND = echo \'Subject: $SUBJECT\n\n$MESSAGE\' | $MAIL_PATH/$MAILER -t $MAILTO
471 # test a number of times, or SKIP to ignore this test.
475 #TEST_START SKIP
483 # You can append SKIP to this label and the options within this
487 # DEFAULTS SKIP
508 # environment, use kernel-install command.
510 #POST_KTEST = ssh root@Test "/usr/bin/kernel-install remove $KERNEL_VERSION"
514 #   build   - only build the kernel, do nothing else
515 #   install - build and install, but do nothing else (does not reboot)
516 #   boot    - build, install, and boot the kernel
517 #   test    - build, boot and if TEST is set, run the test script
519 #   bisect - Perform a bisect on the kernel (see BISECT_TYPE below)
520 #   patchcheck - Do a test on a series of commits in git (see PATCHCHECK below)
528 # The build type is any make config type or special command
530 #   nobuild - skip the clean and build step
531 #   useconfig:/path/to/config - use the given config and run
538 #MAKE_CMD = CC=i386-gcc AS=i386-as make ARCH=i386
542 #BUILD_OPTIONS = -j20
550 #PRE_INSTALL = ssh user@target rm -rf '/lib/modules/*-test*'
558 #POST_INSTALL = ssh user@target /sbin/mkinitrd --allow-missing -f /boot/initramfs-test.img $KERNEL_…
561 #POST_INSTALL = ssh user@target /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION
564 # environment, use kernel-install command.
566 #POST_INSTALL = ssh root@Test "/usr/bin/kernel-install add $KERNEL_VERSION /boot/vmlinuz-$KERNEL_VE…
590 #POST_TEST = cd ${BUILD_DIR}; git reset --hard
597 # patch before each build that is made. Use the POST_BUILD to do a git reset --hard
601 #PRE_BUILD = cd ${BUILD_DIR} && patch -p1 < /tmp/temp.patch
616 #POST_BUILD = cd ${BUILD_DIR} && git reset --hard
667 # The min config that is needed to build for the machine
675 #   $ rm .config
677 #   $ grep '^CONFIG' .config > /home/test/config-min
684 #   # lsmod | cut -d' ' -f1 | xargs rmmod
692 # to the host, and then remove the previous .config and run the
702 #MIN_CONFIG = /home/test/config-min
712 # This option points to the file containing config options that will be prepended
715 # Note, config options in MIN_CONFIG will override these options.
718 #ADD_CONFIG = /home/test/config-broken
769 # (default 600, -1 is to never stop)
773 # a failure is detected, otherwise it will save off the .config,
775 # MACHINE-TEST_TYPE_BUILD_TYPE-fail-yyyymmddhhmmss
783 # set, DIE_ON_FAILURE=0 will not save off the .config, dmesg and
789 # set, the .config, dmesg and bootlog will not be saved if a
794 # Build without doing a make mrproper, or removing .config
895 #POWER_OFF = wget --no-proxy -O /dev/null -q  --auth-no-challenge 'http://admin:admin@power/outlet?…
921 # The variables SSH_USER, MACHINE are defined by the config
925 #SCP_TO_TARGET = echo skip scp for $SRC_FILE $DST_FILE
951 # All options in the config file should be either used by ktest
953 # in the config file is not used, ktest will warn about it and ask
956 # If you don't care if there are non-used options, enable this
957 # option. Be careful though, a non-used option is usually a sign
992 #  not have to translate a test number to a test in the config.
1057 #	build	- bad fails to build
1058 #	boot	- bad builds but fails to boot
1059 #	test	- bad boots but fails a test
1089 #   and you need to skip it. If BISECT_START is defined, it
1101 #   run "git bisect skip" and try again.
1110 #   Will run the bisect with "git bisect start -- arch/x86 kernel/time"
1159 #   0 for good, and non-zero for bad, you can override 0 being
1165 #   0 for good, and non-zero for bad, you can override non-zero being
1179 #   test returns when it should skip the current commit.
1185 #   "abort" or "skip" (without the quotes).
1198 #   MIN_CONFIG = /home/test/config-bisect
1205 #  work, the other does not, and you do not know what config causes
1207 #  The TEST_TYPE config_bisect will bisect the bad config looking for
1208 #  what config causes the failure.
1212 #   You can specify a good config with CONFIG_BISECT_GOOD, otherwise it
1214 #   the config that comes with "make defconfig".
1221 #   It will set half of the good configs within the bad config (note,
1222 #   "set" means to make the bad config match the good config, a config
1223 #   in the good config that is off, will be turned off in the bad
1224 #   config. That is considered a "set").
1226 #   It tests this new config and if it works, it becomes the new good
1227 #   config, otherwise it becomes the new bad config. It continues this
1228 #   process until there's only one config left and it will report that
1229 #   config.
1231 #   The "bad config" can also be a config that is needed to boot but was
1239 #   Although the MIN_CONFIG may be the config it starts with, the
1245 #	build	- bad fails to build
1246 #	boot	- bad builds but fails to boot
1247 #	test	- bad boots but fails a test
1249 #  CONFIG_BISECT is the config that failed to boot
1252 #  This is useful to use just ktest.pl just for the config bisect.
1255 #  the test succeeded or not and continue the config bisect.
1258 #  If you have a good config to start with, then you
1261 #  It will build a config with "make defconfig"
1264 #  Set this to 1 if you want to confirm that the config ktest
1265 #  generates (the bad config with the min config) is still bad.
1266 #  It may be that the min config fixes what broke the bad config
1268 #  Set it to "good" to test only the good config and set it
1269 #  to "bad" to only test the bad config.
1272 #  The config bisect is a separate program that comes with ktest.pl.
1274 #    `pwd`/config-bisect.pl # the location ktest.pl was executed from.
1276 #    `dirname <ktest.pl>`/config-bisect.pl # The directory that holds ktest.pl
1278 #    ${BUILD_DIR}/tools/testing/ktest/config-bisect.pl
1285 #   CONFIG_BISECT = /home/test/config-bad
1286 #   MIN_CONFIG = /home/test/config-min
1295 #  config that you can use against other configs is very useful if
1296 #  someone else has a config that breaks on your code. By only forcing
1300 #  be able to reproduce the reported bug matching the broken config.
1304 #  you to interrupt it, and gives you the current minimum config
1309 #  TODO: add a test version that makes the config do more than just
1314 #  of the configs. If a config is chosen that depends on another
1315 #  config, that config will be checked first. By checking the
1319 #  For example, if a USB device config is chosen and depends on CONFIG_USB,
1326 #   this file as your new min config, and use it to continue the test.
1328 #   This file is not created until a config is found that can be removed.
1334 #  START_MIN_CONFIG is the config to use to start the test with.
1339 #  IGNORE_CONFIG is used to specify a config file that has configs that
1348 #   test if the created config can just boot the machine. If this is
1350 #   config will not only boot the target, but also make sure that the
1351 #   config lets the test succeed. This is useful to make sure the final
1352 #   config that is generated allows network activity (ssh).
1358 #   If it is not defined, it will prompt you to pick which config
1364 #  OUTPUT_MIN_CONFIG = /path/to/config-new-min
1365 #  START_MIN_CONFIG = /path/to/config-min
1366 #  IGNORE_CONFIG = /path/to/config-tested
1382 # specify BUILD_TYPE to tell the test what type of config to use.