aboutsummaryrefslogtreecommitdiffstats
path: root/tools/testing
diff options
context:
space:
mode:
Diffstat (limited to 'tools/testing')
-rw-r--r--tools/testing/ktest/sample.conf90
1 files changed, 89 insertions, 1 deletions
diff --git a/tools/testing/ktest/sample.conf b/tools/testing/ktest/sample.conf
index 03d6e91245fe..e1272746ce8c 100644
--- a/tools/testing/ktest/sample.conf
+++ b/tools/testing/ktest/sample.conf
@@ -390,6 +390,21 @@
390# Example for a virtual guest call "Guest". 390# Example for a virtual guest call "Guest".
391#POWER_OFF = virsh destroy Guest 391#POWER_OFF = virsh destroy Guest
392 392
393# The way to execute a command on the target
394# (default ssh $SSH_USER@$MACHINE $SSH_COMMAND";)
395# The variables SSH_USER, MACHINE and SSH_COMMAND are defined
396#SSH_EXEC = ssh $SSH_USER@$MACHINE $SSH_COMMAND";
397
398# The way to copy a file to the target
399# (default scp $SRC_FILE $SSH_USER@$MACHINE:$DST_FILE)
400# The variables SSH_USER, MACHINE, SRC_FILE and DST_FILE are defined.
401#SCP_TO_TARGET = scp $SRC_FILE $SSH_USER@$MACHINE:$DST_FILE
402
403# The nice way to reboot the target
404# (default ssh $SSH_USER@$MACHINE reboot)
405# The variables SSH_USER and MACHINE are defined.
406#REBOOT = ssh $SSH_USER@$MACHINE reboot
407
393#### Per test run options #### 408#### Per test run options ####
394# The following options are only allowed in TEST_START sections. 409# The following options are only allowed in TEST_START sections.
395# They are ignored in the DEFAULTS sections. 410# They are ignored in the DEFAULTS sections.
@@ -442,7 +457,7 @@
442# CHECKOUT = mybranch 457# CHECKOUT = mybranch
443# PATCHCHECK_TYPE = boot 458# PATCHCHECK_TYPE = boot
444# PATCHCHECK_START = 747e94ae3d1b4c9bf5380e569f614eb9040b79e7 459# PATCHCHECK_START = 747e94ae3d1b4c9bf5380e569f614eb9040b79e7
445# PATCHCHEKC_END = HEAD~2 460# PATCHCHECK_END = HEAD~2
446# 461#
447# 462#
448# 463#
@@ -520,3 +535,76 @@
520# BISECT_BAD = b5153163ed580e00c67bdfecb02b2e3843817b3e 535# BISECT_BAD = b5153163ed580e00c67bdfecb02b2e3843817b3e
521# BISECT_TYPE = build 536# BISECT_TYPE = build
522# MIN_CONFIG = /home/test/config-bisect 537# MIN_CONFIG = /home/test/config-bisect
538#
539#
540#
541# For TEST_TYPE = config_bisect
542#
543# In those cases that you have two different configs. One of them
544# work, the other does not, and you do not know what config causes
545# the problem.
546# The TEST_TYPE config_bisect will bisect the bad config looking for
547# what config causes the failure.
548#
549# The way it works is this:
550#
551# First it finds a config to work with. Since a different version, or
552# MIN_CONFIG may cause different dependecies, it must run through this
553# preparation.
554#
555# Overwrites any config set in the bad config with a config set in
556# either the MIN_CONFIG or ADD_CONFIG. Thus, make sure these configs
557# are minimal and do not disable configs you want to test:
558# (ie. # CONFIG_FOO is not set).
559#
560# An oldconfig is run on the bad config and any new config that
561# appears will be added to the configs to test.
562#
563# Finally, it generates a config with the above result and runs it
564# again through make oldconfig to produce a config that should be
565# satisfied by kconfig.
566#
567# Then it starts the bisect.
568#
569# The configs to test are cut in half. If all the configs in this
570# half depend on a config in the other half, then the other half
571# is tested instead. If no configs are enabled by either half, then
572# this means a circular dependency exists and the test fails.
573#
574# A config is created with the test half, and the bisect test is run.
575#
576# If the bisect succeeds, then all configs in the generated config
577# are removed from the configs to test and added to the configs that
578# will be enabled for all builds (they will be enabled, but not be part
579# of the configs to examine).
580#
581# If the bisect fails, then all test configs that were not enabled by
582# the config file are removed from the test. These configs will not
583# be enabled in future tests. Since current config failed, we consider
584# this to be a subset of the config that we started with.
585#
586# When we are down to one config, it is considered the bad config.
587#
588# Note, the config chosen may not be the true bad config. Due to
589# dependencies and selections of the kbuild system, mulitple
590# configs may be needed to cause a failure. If you disable the
591# config that was found and restart the test, if the test fails
592# again, it is recommended to rerun the config_bisect with a new
593# bad config without the found config enabled.
594#
595# The option BUILD_TYPE will be ignored.
596#
597# CONFIG_BISECT_TYPE is the type of test to perform:
598# build - bad fails to build
599# boot - bad builds but fails to boot
600# test - bad boots but fails a test
601#
602# CONFIG_BISECT is the config that failed to boot
603#
604# Example:
605# TEST_START
606# TEST_TYPE = config_bisect
607# CONFIG_BISECT_TYPE = build
608# CONFIG_BISECT = /home/test/˘onfig-bad
609# MIN_CONFIG = /home/test/config-min
610#