2 # Generic config for a machine
5 # Name your machine (the DNS name, what you ssh to)
8 # BOX can be different than foo, if the machine BOX has
9 # multiple partitions with different systems installed. For example,
10 # you may have a i386 and x86_64 installation on a test box.
11 # If this is the case, MACHINE defines the way to connect to the
12 # machine, which may be different between which system the machine
13 # is booting into. BOX is used for the scripts to reboot and power cycle
14 # the machine, where it does not matter which system the machine boots into.
18 # Define a way to read the console
19 CONSOLE = stty -F /dev/ttyS0 115200 parodd; cat /dev/ttyS0
21 # The include files will set up the type of test to run. Just set TEST to
22 # which test you want to run.
24 # TESTS = patchcheck, randconfig, boot, test, config-bisect, bisect, min-config
26 # See the include/*.conf files that define these tests
30 # Some tests may have more than one test to run. Define MULTI := 1 to run
34 # In case you want to differentiate which type of system you are testing
37 # REBOOT = none, error, fail, empty
38 # See include/defaults.conf
41 # The defaults file will set up various settings that can be used by all
43 INCLUDE include/defaults.conf
45 # In case you need to add a patch for a bisect or something
46 #PRE_BUILD = patch -p1 < ${THIS_DIR}/fix.patch
48 # Reset the repo after the build and remove all 'test' modules from the target
49 # Notice that DO_POST_BUILD is a variable (defined by ':=') and POST_BUILD
50 # is the option (defined by '=')
52 DO_POST_BUILD := git reset --hard
53 POST_BUILD = ${SSH} 'rm -rf /lib/modules/*-test*'; ${DO_POST_BUILD}
55 # The following files each handle a different test case.
56 # Having them included allows you to set up more than one machine and share
58 INCLUDE include/patchcheck.conf
59 INCLUDE include/tests.conf
60 INCLUDE include/bisect.conf
61 INCLUDE include/min-config.conf