| .. | .. |
|---|
| 10 | 10 | # |
|---|
| 11 | 11 | |
|---|
| 12 | 12 | # Options set in the beginning of the file are considered to be |
|---|
| 13 | | -# default options. These options can be overriden by test specific |
|---|
| 13 | +# default options. These options can be overridden by test specific |
|---|
| 14 | 14 | # options, with the following exceptions: |
|---|
| 15 | 15 | # |
|---|
| 16 | 16 | # LOG_FILE |
|---|
| .. | .. |
|---|
| 204 | 204 | # |
|---|
| 205 | 205 | # This config file can also contain "config variables". |
|---|
| 206 | 206 | # These are assigned with ":=" instead of the ktest option |
|---|
| 207 | | -# assigment "=". |
|---|
| 207 | +# assignment "=". |
|---|
| 208 | 208 | # |
|---|
| 209 | 209 | # The difference between ktest options and config variables |
|---|
| 210 | 210 | # is that config variables can be used multiple times, |
|---|
| .. | .. |
|---|
| 263 | 263 | #### Using options in other options #### |
|---|
| 264 | 264 | # |
|---|
| 265 | 265 | # Options that are defined in the config file may also be used |
|---|
| 266 | | -# by other options. All options are evaulated at time of |
|---|
| 266 | +# by other options. All options are evaluated at time of |
|---|
| 267 | 267 | # use (except that config variables are evaluated at config |
|---|
| 268 | 268 | # processing time). |
|---|
| 269 | 269 | # |
|---|
| .. | .. |
|---|
| 349 | 349 | # option to boot to with GRUB_REBOOT |
|---|
| 350 | 350 | #GRUB_FILE = /boot/grub2/grub.cfg |
|---|
| 351 | 351 | |
|---|
| 352 | | -# The tool for REBOOT_TYPE = grub2 to set the next reboot kernel |
|---|
| 352 | +# The tool for REBOOT_TYPE = grub2 or grub2bls to set the next reboot kernel |
|---|
| 353 | 353 | # to boot into (one shot mode). |
|---|
| 354 | 354 | # (default grub2_reboot) |
|---|
| 355 | 355 | #GRUB_REBOOT = grub2_reboot |
|---|
| 356 | 356 | |
|---|
| 357 | 357 | # The grub title name for the test kernel to boot |
|---|
| 358 | | -# (Only mandatory if REBOOT_TYPE = grub or grub2) |
|---|
| 358 | +# (Only mandatory if REBOOT_TYPE = grub or grub2 or grub2bls) |
|---|
| 359 | 359 | # |
|---|
| 360 | 360 | # Note, ktest.pl will not update the grub menu.lst, you need to |
|---|
| 361 | 361 | # manually add an option for the test. ktest.pl will search |
|---|
| .. | .. |
|---|
| 373 | 373 | # for: menuentry 'Test Kernel' |
|---|
| 374 | 374 | # do a: GRUB_MENU = 'Test Kernel' |
|---|
| 375 | 375 | # For customizing, add your entry in /etc/grub.d/40_custom. |
|---|
| 376 | +# |
|---|
| 377 | +# For grub2bls, a search of "title"s are done. The menu is found |
|---|
| 378 | +# by searching for the contents of GRUB_MENU in the line that starts |
|---|
| 379 | +# with "title". |
|---|
| 376 | 380 | # |
|---|
| 377 | 381 | #GRUB_MENU = Test Kernel |
|---|
| 378 | 382 | |
|---|
| .. | .. |
|---|
| 438 | 442 | # Users can cancel the test by Ctrl^C |
|---|
| 439 | 443 | # (default 0) |
|---|
| 440 | 444 | #EMAIL_WHEN_CANCELED = 1 |
|---|
| 445 | +# |
|---|
| 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 |
|---|
| 448 | +# be included in the email that is sent. |
|---|
| 449 | +# It is possible that the log may be very large, in which case, |
|---|
| 450 | +# only the last amount of the log should be sent. To limit how |
|---|
| 451 | +# much of the log is sent, set MAIL_MAX_SIZE. This will be the |
|---|
| 452 | +# size in bytes of the last portion of the log of the failed |
|---|
| 453 | +# test file. That is, if this is set to 100000, then only the |
|---|
| 454 | +# last 100 thousand bytes of the log file will be included in |
|---|
| 455 | +# the email. |
|---|
| 456 | +# (default undef) |
|---|
| 457 | +#MAIL_MAX_SIZE = 1000000 |
|---|
| 441 | 458 | |
|---|
| 442 | 459 | # Start a test setup. If you leave this off, all options |
|---|
| 443 | 460 | # will be default and the test will run once. |
|---|
| .. | .. |
|---|
| 479 | 496 | # default (undefined) |
|---|
| 480 | 497 | #POST_KTEST = ${SSH} ~/dismantle_test |
|---|
| 481 | 498 | |
|---|
| 499 | +# If you want to remove the kernel entry in Boot Loader Specification (BLS) |
|---|
| 500 | +# environment, use kernel-install command. |
|---|
| 501 | +# Here's the example: |
|---|
| 502 | +#POST_KTEST = ssh root@Test "/usr/bin/kernel-install remove $KERNEL_VERSION" |
|---|
| 503 | + |
|---|
| 482 | 504 | # The default test type (default test) |
|---|
| 483 | 505 | # The test types may be: |
|---|
| 484 | 506 | # build - only build the kernel, do nothing else |
|---|
| .. | .. |
|---|
| 496 | 518 | #TEST = ssh user@machine /root/run_test |
|---|
| 497 | 519 | |
|---|
| 498 | 520 | # The build type is any make config type or special command |
|---|
| 499 | | -# (default randconfig) |
|---|
| 521 | +# (default oldconfig) |
|---|
| 500 | 522 | # nobuild - skip the clean and build step |
|---|
| 501 | 523 | # useconfig:/path/to/config - use the given config and run |
|---|
| 502 | 524 | # oldconfig on it. |
|---|
| .. | .. |
|---|
| 530 | 552 | # or on some systems: |
|---|
| 531 | 553 | #POST_INSTALL = ssh user@target /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION |
|---|
| 532 | 554 | |
|---|
| 555 | +# If you want to add the kernel entry in Boot Loader Specification (BLS) |
|---|
| 556 | +# environment, use kernel-install command. |
|---|
| 557 | +# Here's the example: |
|---|
| 558 | +#POST_INSTALL = ssh root@Test "/usr/bin/kernel-install add $KERNEL_VERSION /boot/vmlinuz-$KERNEL_VERSION" |
|---|
| 559 | + |
|---|
| 533 | 560 | # If for some reason you just want to boot the kernel and you do not |
|---|
| 534 | 561 | # want the test to install anything new. For example, you may just want |
|---|
| 535 | 562 | # to boot test the same kernel over and over and do not want to go through |
|---|
| .. | .. |
|---|
| 542 | 569 | # |
|---|
| 543 | 570 | # default (undefined) |
|---|
| 544 | 571 | #PRE_TEST = ${SSH} reboot_to_special_kernel |
|---|
| 572 | + |
|---|
| 573 | +# To kill the entire test if PRE_TEST is defined but fails set this |
|---|
| 574 | +# to 1. |
|---|
| 575 | +# (default 0) |
|---|
| 576 | +#PRE_TEST_DIE = 1 |
|---|
| 545 | 577 | |
|---|
| 546 | 578 | # If there is a command you want to run after the individual test case |
|---|
| 547 | 579 | # completes, then you can set this option. |
|---|
| .. | .. |
|---|
| 592 | 624 | # |
|---|
| 593 | 625 | # For REBOOT_TYPE = grub2, you must define both GRUB_MENU and |
|---|
| 594 | 626 | # GRUB_FILE. |
|---|
| 627 | +# |
|---|
| 628 | +# For REBOOT_TYPE = grub2bls, you must define GRUB_MENU. |
|---|
| 595 | 629 | # |
|---|
| 596 | 630 | # For REBOOT_TYPE = syslinux, you must define SYSLINUX_LABEL, and |
|---|
| 597 | 631 | # perhaps modify SYSLINUX (default extlinux) and SYSLINUX_PATH |
|---|
| .. | .. |
|---|
| 691 | 725 | |
|---|
| 692 | 726 | # Line to define a successful boot up in console output. |
|---|
| 693 | 727 | # This is what the line contains, not the entire line. If you need |
|---|
| 694 | | -# the entire line to match, then use regural expression syntax like: |
|---|
| 728 | +# the entire line to match, then use regular expression syntax like: |
|---|
| 695 | 729 | # (do not add any quotes around it) |
|---|
| 696 | 730 | # |
|---|
| 697 | 731 | # SUCCESS_LINE = ^MyBox Login:$ |
|---|
| .. | .. |
|---|
| 775 | 809 | # is issued instead of a reboot. |
|---|
| 776 | 810 | # CONNECT_TIMEOUT = 25 |
|---|
| 777 | 811 | |
|---|
| 812 | +# The timeout in seconds for how long to wait for any running command |
|---|
| 813 | +# to timeout. If not defined, it will let it go indefinitely. |
|---|
| 814 | +# (default undefined) |
|---|
| 815 | +#RUN_TIMEOUT = 600 |
|---|
| 816 | + |
|---|
| 778 | 817 | # In between tests, a reboot of the box may occur, and this |
|---|
| 779 | 818 | # is the time to wait for the console after it stops producing |
|---|
| 780 | 819 | # output. Some machines may not produce a large lag on reboot |
|---|
| .. | .. |
|---|
| 823 | 862 | # (ignored if POWEROFF_ON_SUCCESS is set) |
|---|
| 824 | 863 | #REBOOT_ON_SUCCESS = 1 |
|---|
| 825 | 864 | |
|---|
| 826 | | -# In case there are isses with rebooting, you can specify this |
|---|
| 865 | +# In case there are issues with rebooting, you can specify this |
|---|
| 827 | 866 | # to always powercycle after this amount of time after calling |
|---|
| 828 | 867 | # reboot. |
|---|
| 829 | 868 | # Note, POWERCYCLE_AFTER_REBOOT = 0 does NOT disable it. It just |
|---|
| .. | .. |
|---|
| 832 | 871 | # (default undefined) |
|---|
| 833 | 872 | #POWERCYCLE_AFTER_REBOOT = 5 |
|---|
| 834 | 873 | |
|---|
| 835 | | -# In case there's isses with halting, you can specify this |
|---|
| 874 | +# In case there's issues with halting, you can specify this |
|---|
| 836 | 875 | # to always poweroff after this amount of time after calling |
|---|
| 837 | 876 | # halt. |
|---|
| 838 | 877 | # Note, POWEROFF_AFTER_HALT = 0 does NOT disable it. It just |
|---|
| .. | .. |
|---|
| 886 | 925 | # (default ssh $SSH_USER@$MACHINE reboot) |
|---|
| 887 | 926 | # The variables SSH_USER and MACHINE are defined. |
|---|
| 888 | 927 | #REBOOT = ssh $SSH_USER@$MACHINE reboot |
|---|
| 928 | + |
|---|
| 929 | +# The return code of REBOOT |
|---|
| 930 | +# (default 255) |
|---|
| 931 | +#REBOOT_RETURN_CODE = 255 |
|---|
| 889 | 932 | |
|---|
| 890 | 933 | # The way triple faults are detected is by testing the kernel |
|---|
| 891 | 934 | # banner. If the kernel banner for the kernel we are testing is |
|---|
| .. | .. |
|---|
| 952 | 995 | # |
|---|
| 953 | 996 | # PATCHCHECK_START is required and is the first patch to |
|---|
| 954 | 997 | # test (the SHA1 of the commit). You may also specify anything |
|---|
| 955 | | -# that git checkout allows (branch name, tage, HEAD~3). |
|---|
| 998 | +# that git checkout allows (branch name, tag, HEAD~3). |
|---|
| 956 | 999 | # |
|---|
| 957 | 1000 | # PATCHCHECK_END is the last patch to check (default HEAD) |
|---|
| 958 | 1001 | # |
|---|
| .. | .. |
|---|
| 974 | 1017 | # IGNORE_WARNINGS is set for the given commit's sha1 |
|---|
| 975 | 1018 | # |
|---|
| 976 | 1019 | # IGNORE_WARNINGS can be used to disable the failure of patchcheck |
|---|
| 977 | | -# on a particuler commit (SHA1). You can add more than one commit |
|---|
| 1020 | +# on a particular commit (SHA1). You can add more than one commit |
|---|
| 978 | 1021 | # by adding a list of SHA1s that are space delimited. |
|---|
| 979 | 1022 | # |
|---|
| 980 | 1023 | # If BUILD_NOCLEAN is set, then make mrproper will not be run on |
|---|
| .. | .. |
|---|
| 1073 | 1116 | # whatever reason. (Can't reboot, want to inspect each iteration) |
|---|
| 1074 | 1117 | # Doing a BISECT_MANUAL will have the test wait for you to |
|---|
| 1075 | 1118 | # tell it if the test passed or failed after each iteration. |
|---|
| 1076 | | -# This is basicall the same as running git bisect yourself |
|---|
| 1119 | +# This is basically the same as running git bisect yourself |
|---|
| 1077 | 1120 | # but ktest will rebuild and install the kernel for you. |
|---|
| 1078 | 1121 | # |
|---|
| 1079 | 1122 | # BISECT_CHECK = 1 (optional, default 0) |
|---|
| .. | .. |
|---|
| 1219 | 1262 | # |
|---|
| 1220 | 1263 | # CONFIG_BISECT_EXEC (optional) |
|---|
| 1221 | 1264 | # The config bisect is a separate program that comes with ktest.pl. |
|---|
| 1222 | | -# By befault, it will look for: |
|---|
| 1265 | +# By default, it will look for: |
|---|
| 1223 | 1266 | # `pwd`/config-bisect.pl # the location ktest.pl was executed from. |
|---|
| 1224 | 1267 | # If it does not find it there, it will look for: |
|---|
| 1225 | 1268 | # `dirname <ktest.pl>`/config-bisect.pl # The directory that holds ktest.pl |
|---|