Lines Matching +full:fails +full:- +full:without +full:- +full:test +full:- +full:cd
13 # default options. These options can be overridden by test specific
21 # Test specific options are set after the label:
25 # The options after a TEST_START label are specific to that test.
26 # Each TEST_START label will set up a new test. If you want to
27 # perform a test more than once, you can add the ITERATE label
28 # to it followed by the number of times you want that test
29 # to iterate. If the ITERATE is left off, the test will only
34 # You can skip a test by adding SKIP (before or after the ITERATE
43 # The SKIP label causes the options and the test itself to be ignored.
45 # only enabling the ones you want to use for a current test run.
49 # after the test options to keep the test options at the top
51 # test cases (but not in the middle of a single test case)
54 # MIN_CONFIG = /home/test/config-test1
57 # MIN_CONFIG = /home/test/config-default
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
63 # with MIN_CONFIG with /home/test/config-default.
68 # MIN_CONFIG = /home/test/config-use-sometimes
71 # MIN_CONFIG = /home/test/config-most-times
76 # may only be declared once per test or default. If you have
77 # the same option name under the same test or as default
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
166 # Notice the use of parentheses. Without any parentheses the above would be
177 # file can include other files, add new test cases or default
222 # TEST_CASE := ssh ${USER}@${TARGET} /path/to/my/test
226 # TEST = ${TEST_CASE}
230 # TEST = ${TEST_CASE}
236 # TEST = ${TEST_CASE}
240 # TEST = ${TEST_CASE}
242 # TEST_DIR := /home/me/test
245 # OUTPUT_DIR = ${TEST_DIR}/test
276 # TEST = ssh root@${MACHINE} /path/to/test
278 # The option will be used per test case. Thus:
280 # TEST_TYPE = test
281 # TEST = ssh root@{MACHINE}
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
296 # may be overridden by test options.
298 # The machine hostname that you will test
306 #BUILD_DIR = /home/test/linux.git
310 #OUTPUT_DIR = /home/test/build/target
316 # The place to put your image on the test machine
317 #TARGET_IMAGE = /boot/vmlinuz-test
322 #POWER_CYCLE = wget --no-proxy -O /dev/null -q --auth-no-challenge 'http://admin:admin@power/outle…
331 #CONSOLE = nc -d localhost 3001
343 # Required version ending to differentiate the test
345 #LOCALVERSION = -test
357 # The grub title name for the test kernel to boot
361 # manually add an option for the test. ktest.pl will search
365 # For example, if in the /boot/grub/menu.lst the test kernel title has:
366 # title Test Kernel
367 # kernel vmlinuz-test
373 # for: menuentry 'Test Kernel'
374 # do a: GRUB_MENU = 'Test Kernel'
381 #GRUB_MENU = Test Kernel
385 # test kernel.
395 # test kernel in the syslinux config file.
397 #SYSLINUX_LABEL = "test-kernel"
399 # A script to reboot the target into the test kernel
424 # MAIL_COMMAND = echo \'Subject: $SUBJECT\n\n$MESSAGE\' | $MAIL_PATH/$MAILER -t $MAILTO
426 # MAIL_COMMAND = "$MAIL_PATH/$MAILER -s \'$SUBJECT\' $MAILTO <<< \'$MESSAGE\'
432 #MAIL_COMMAND = echo \'Subject: $SUBJECT\n\n$MESSAGE\' | $MAIL_PATH/$MAILER -t $MAILTO
442 # Users can cancel the test by Ctrl^C
446 # If a test ends with an error and EMAIL_ON_ERROR is set as well
447 # as a LOG_FILE is defined, then the log of the failing test will
453 # test file. That is, if this is set to 100000, then only the
459 # Start a test setup. If you leave this off, all options
460 # will be default and the test will run once.
463 # test a number of times, or SKIP to ignore this test.
481 # If you want to execute some command before the first test runs
483 # or an option in the first test case. All other test cases will
484 # ignore it. If both the default and first test have this option
485 # set, then the first test will take precedence.
492 # default or any test case can override it. If multiple test cases
493 # set this option, then the last test case that set it will take
500 # environment, use kernel-install command.
502 #POST_KTEST = ssh root@Test "/usr/bin/kernel-install remove $KERNEL_VERSION"
504 # The default test type (default test)
505 # The test types may be:
506 # build - only build the kernel, do nothing else
507 # install - build and install, but do nothing else (does not reboot)
508 # boot - build, install, and boot the kernel
509 # test - build, boot and if TEST is set, run the test script
510 # (If TEST is not set, it defaults back to boot)
511 # bisect - Perform a bisect on the kernel (see BISECT_TYPE below)
512 # patchcheck - Do a test on a series of commits in git (see PATCHCHECK below)
513 #TEST_TYPE = test
515 # Test to run if there is a successful boot and TEST_TYPE is test.
518 #TEST = ssh user@machine /root/run_test
522 # nobuild - skip the clean and build step
523 # useconfig:/path/to/config - use the given config and run
530 #MAKE_CMD = CC=i386-gcc AS=i386-as make ARCH=i386
534 #BUILD_OPTIONS = -j20
542 #PRE_INSTALL = ssh user@target rm -rf '/lib/modules/*-test*'
550 #POST_INSTALL = ssh user@target /sbin/mkinitrd --allow-missing -f /boot/initramfs-test.img $KERNEL_…
553 #POST_INSTALL = ssh user@target /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION
556 # environment, use kernel-install command.
558 #POST_INSTALL = ssh root@Test "/usr/bin/kernel-install add $KERNEL_VERSION /boot/vmlinuz-$KERNEL_VE…
561 # want the test to install anything new. For example, you may just want
562 # to boot test the same kernel over and over and do not want to go through
567 # If there is a command that you want to run before the individual test
573 # To kill the entire test if PRE_TEST is defined but fails set this
578 # If there is a command you want to run after the individual test case
582 #POST_TEST = cd ${BUILD_DIR}; git reset --hard
588 # fix a unrelated bug to perform a patchcheck test. This will apply the
589 # patch before each build that is made. Use the POST_BUILD to do a git reset --hard
593 #PRE_BUILD = cd ${BUILD_DIR} && patch -p1 < /tmp/temp.patch
595 # To specify if the test should fail if the PRE_BUILD fails,
608 #POST_BUILD = cd ${BUILD_DIR} && git reset --hard
610 # To specify if the test should fail if the POST_BUILD fails,
616 # Way to reboot the box to the test kernel.
635 # The test will not modify that file.
641 # test image.
666 # $ cd linux.git
669 # $ grep '^CONFIG' .config > /home/test/config-min
676 # # lsmod | cut -d' ' -f1 | xargs rmmod
687 # test may fail.
694 #MIN_CONFIG = /home/test/config-min
710 #ADD_CONFIG = /home/test/config-broken
719 #LOG_FILE = /home/test/logfiles/target.log
739 # a new test kernel to it. Otherwise ktest.pl will wait till
745 # a specified time to stop the test after success is recommended.
751 # a specified time to stop the test after failure is recommended.
757 # a specified time to stop the test if it never succeeds nor fails
761 # (default 600, -1 is to never stop)
764 # Stop testing if a build fails. If set, the script will end if
767 # MACHINE-TEST_TYPE_BUILD_TYPE-fail-yyyymmddhhmmss
778 #STORE_FAILURES = /home/test/failures
782 # test succeeds.
784 #STORE_SUCCESSES = /home/test/successes
786 # Build without doing a make mrproper, or removing .config
790 # As the test reads the console, after it hits the SUCCESS_LINE
800 # not want the test to fail just because the system was in
801 # the process of rebooting to the test kernel.
805 # The timeout in seconds when to test if the box can be rebooted
817 # when rebooting to the test kernel. This sleep time happens
818 # after a test has completed and we are about to start running
819 # another test. If a reboot to the reliable kernel happens,
821 # before starting the next test.
832 # If for some reason, the console is outputting content without
856 # Reboot the target after all test completed successfully (default 1)
882 #POWER_OFF = wget --no-proxy -O /dev/null -q --auth-no-challenge 'http://admin:admin@power/outlet?…
943 # If you don't care if there are non-used options, enable this
944 # option. Be careful though, a non-used option is usually a sign
950 # traces, ktest.pl will detect these and fail a boot or test run
952 # call traces, and will not fail a test if the kernel produces
957 #### Per test run options ####
969 # to checkout the given branch before running the TEST. If you
976 # If you want the test to have a name that is displayed in
977 # the test result banner at the end of the test, then use this
979 # not have to translate a test number to a test in the config.
992 # test (the SHA1 of the commit). You may also specify anything
1007 # PATCHCHECK_TYPE is required and is the type of test to run:
1008 # build, boot, test.
1010 # Note, the build test will look for warnings, if a warning occurred
1022 # make mrproper. This helps speed up the test.
1043 # BISECT_TYPE is the type of test to perform:
1044 # build - bad fails to build
1045 # boot - bad builds but fails to boot
1046 # test - bad boots but fails a test
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
1074 # As with BISECT_REPLAY, if the test failed on a commit that
1083 # If BISECT_TYPE is set to test but the build fails, ktest will
1084 # simply fail the test and end their. You could use BISECT_REPLAY
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
1113 # tell it if the test passed or failed after each iteration.
1121 # out BISECT_BAD and makes sure it fails, then it will check
1125 # You can limit the test to just check BISECT_GOOD or
1133 # test is ran before it says the kernel is good. The first failure
1145 # In case the specificed test returns something other than just
1146 # 0 for good, and non-zero for bad, you can override 0 being
1151 # In case the specificed test returns something other than just
1152 # 0 for good, and non-zero for bad, you can override non-zero being
1157 # If you need to abort the bisect if the test discovers something
1159 # code returned by the test in order to abort the bisect.
1163 # If the test detects that the current commit is neither good
1166 # test returns when it should skip the current commit.
1172 # "abort" or "skip" (without the quotes).
1185 # MIN_CONFIG = /home/test/config-bisect
1223 # If you stop the test, you can copy them to a new location to
1231 # CONFIG_BISECT_TYPE is the type of test to perform:
1232 # build - bad fails to build
1233 # boot - bad builds but fails to boot
1234 # test - bad boots but fails a test
1242 # the test succeeded or not and continue the config bisect.
1254 # and the test will not return a result.
1255 # Set it to "good" to test only the good config and set it
1256 # to "bad" to only test the bad config.
1261 # `pwd`/config-bisect.pl # the location ktest.pl was executed from.
1263 # `dirname <ktest.pl>`/config-bisect.pl # The directory that holds ktest.pl
1265 # ${BUILD_DIR}/tools/testing/ktest/config-bisect.pl
1272 # CONFIG_BISECT = /home/test/config-bad
1273 # MIN_CONFIG = /home/test/config-min
1290 # test over night, or perhaps over the weekend. But it also allows
1294 # Note, this test automatically assumes a BUILD_TYPE of oldconfig
1295 # and its test type acts like boot.
1296 # TODO: add a test version that makes the config do more than just
1299 # To save time, the test does not just grab any option and test
1312 # be created from the MIN_CONFIG. If you interrupt the test, set
1313 # this file as your new min config, and use it to continue the test.
1314 # This file does not need to exist on start of test.
1321 # START_MIN_CONFIG is the config to use to start the test with.
1329 # file if you intend on interrupting the test and running it where
1334 # MIN_CONFIG_TYPE can be either 'boot' or 'test'. With 'boot' it will
1335 # test if the created config can just boot the machine. If this is
1336 # set to 'test', then the TEST option must be defined and the created
1338 # config lets the test succeed. This is useful to make sure the final
1351 # OUTPUT_MIN_CONFIG = /path/to/config-new-min
1352 # START_MIN_CONFIG = /path/to/config-min
1353 # IGNORE_CONFIG = /path/to/config-tested
1354 # MIN_CONFIG_TYPE = test
1355 # TEST = ssh ${USER}@${MACHINE} echo hi
1365 # The test "make_warnings_file" will let you create a new warnings
1368 # What this test does is to run just a build, you still need to
1369 # specify BUILD_TYPE to tell the test what type of config to use.
1370 # A BUILD_TYPE of nobuild will fail this test.
1372 # The test will do the build and scan for all warnings. Any warning