path: root/tools/testing/ktest/sample.conf
diff options
authorSteven Rostedt <srostedt@redhat.com>2012-05-21 17:13:40 -0400
committerSteven Rostedt <rostedt@goodmis.org>2012-05-21 17:13:40 -0400
commitccc513b688e1f409c03cfaa7117cda778331f6fb (patch)
tree9a3e553d7734f050dfe7ac981980ae51fd61c9b0 /tools/testing/ktest/sample.conf
parentktest: Fix kernelrevision with POST_BUILD (diff)
ktest: Add MIN_CONFIG_TYPE to allow making a minum .config that has network
Add a MIN_CONFIG_TYPE that can be set to 'test' or 'boot'. The default is 'boot' which is what make_min_config has done previously: makes a config file that is the minimum needed to boot the target. But when MIN_CONFIG_TYPE is set to 'test', not only must the target boot, but it must also successfully run the TEST. This allows the creation of a config file that is the minimum to boot and also perform ssh to the target, or anything else a developer wants. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to '')
1 files changed, 10 insertions, 0 deletions
diff --git a/tools/testing/ktest/sample.conf b/tools/testing/ktest/sample.conf
index b682456afda8..1c1b7dc13430 100644
--- a/tools/testing/ktest/sample.conf
+++ b/tools/testing/ktest/sample.conf
@@ -1105,10 +1105,20 @@
# and will not be tested again in later runs.
# (optional)
+# MIN_CONFIG_TYPE can be either 'boot' or 'test'. With 'boot' it will
+# test if the created config can just boot the machine. If this is
+# set to 'test', then the TEST option must be defined and the created
+# config will not only boot the target, but also make sure that the
+# config lets the test succeed. This is useful to make sure the final
+# config that is generated allows network activity (ssh).
+# (optional)
# Example:
# TEST_TYPE = make_min_config
# OUTPUT_MIN_CONFIG = /path/to/config-new-min
# START_MIN_CONFIG = /path/to/config-min
# IGNORE_CONFIG = /path/to/config-tested
+# TEST = ssh ${USER}@${MACHINE} echo hi