1 # 1 #
2 # Config file for ktest.pl 2 # Config file for ktest.pl
3 # 3 #
4 # Place your customized version of this, in th <<
5 # ktest.pl is run from. By default, ktest.pl w <<
6 # called "ktest.conf", but you can name it any <<
7 # the name of your config file as the first ar <<
8 # <<
9 # Note, all paths must be absolute 4 # Note, all paths must be absolute
10 # 5 #
11 6
12 # Options set in the beginning of the file are 7 # Options set in the beginning of the file are considered to be
13 # default options. These options can be overri !! 8 # default options. These options can be overriden by test specific
14 # options, with the following exceptions: 9 # options, with the following exceptions:
15 # 10 #
16 # LOG_FILE 11 # LOG_FILE
17 # CLEAR_LOG 12 # CLEAR_LOG
18 # POWEROFF_ON_SUCCESS 13 # POWEROFF_ON_SUCCESS
19 # REBOOT_ON_SUCCESS 14 # REBOOT_ON_SUCCESS
20 # 15 #
21 # Test specific options are set after the labe 16 # Test specific options are set after the label:
22 # 17 #
23 # TEST_START 18 # TEST_START
24 # 19 #
25 # The options after a TEST_START label are spe 20 # The options after a TEST_START label are specific to that test.
26 # Each TEST_START label will set up a new test 21 # Each TEST_START label will set up a new test. If you want to
27 # perform a test more than once, you can add t 22 # perform a test more than once, you can add the ITERATE label
28 # to it followed by the number of times you wa 23 # to it followed by the number of times you want that test
29 # to iterate. If the ITERATE is left off, the 24 # to iterate. If the ITERATE is left off, the test will only
30 # be performed once. 25 # be performed once.
31 # 26 #
32 # TEST_START ITERATE 10 27 # TEST_START ITERATE 10
33 # 28 #
34 # You can skip a test by adding SKIP (before o 29 # You can skip a test by adding SKIP (before or after the ITERATE
35 # and number) 30 # and number)
36 # 31 #
37 # TEST_START SKIP 32 # TEST_START SKIP
38 # 33 #
39 # TEST_START SKIP ITERATE 10 34 # TEST_START SKIP ITERATE 10
40 # 35 #
41 # TEST_START ITERATE 10 SKIP 36 # TEST_START ITERATE 10 SKIP
42 # 37 #
43 # The SKIP label causes the options and the te 38 # The SKIP label causes the options and the test itself to be ignored.
44 # This is useful to set up several different t 39 # This is useful to set up several different tests in one config file, and
45 # only enabling the ones you want to use for a 40 # only enabling the ones you want to use for a current test run.
46 # 41 #
47 # You can add default options anywhere in the 42 # You can add default options anywhere in the file as well
48 # with the DEFAULTS tag. This allows you to ha 43 # with the DEFAULTS tag. This allows you to have default options
49 # after the test options to keep the test opti 44 # after the test options to keep the test options at the top
50 # of the file. You can even place the DEFAULTS 45 # of the file. You can even place the DEFAULTS tag between
51 # test cases (but not in the middle of a singl 46 # test cases (but not in the middle of a single test case)
52 # 47 #
53 # TEST_START 48 # TEST_START
54 # MIN_CONFIG = /home/test/config-test1 49 # MIN_CONFIG = /home/test/config-test1
55 # 50 #
56 # DEFAULTS 51 # DEFAULTS
57 # MIN_CONFIG = /home/test/config-default 52 # MIN_CONFIG = /home/test/config-default
58 # 53 #
59 # TEST_START ITERATE 10 54 # TEST_START ITERATE 10
60 # 55 #
61 # The above will run the first test with MIN_C 56 # The above will run the first test with MIN_CONFIG set to
62 # /home/test/config-test-1. Then 10 tests will 57 # /home/test/config-test-1. Then 10 tests will be executed
63 # with MIN_CONFIG with /home/test/config-defau 58 # with MIN_CONFIG with /home/test/config-default.
64 # 59 #
65 # You can also disable defaults with the SKIP 60 # You can also disable defaults with the SKIP option
66 # 61 #
67 # DEFAULTS SKIP 62 # DEFAULTS SKIP
68 # MIN_CONFIG = /home/test/config-use-sometimes 63 # MIN_CONFIG = /home/test/config-use-sometimes
69 # 64 #
70 # DEFAULTS 65 # DEFAULTS
71 # MIN_CONFIG = /home/test/config-most-times 66 # MIN_CONFIG = /home/test/config-most-times
72 # 67 #
73 # The above will ignore the first MIN_CONFIG. 68 # The above will ignore the first MIN_CONFIG. If you want to
74 # use the first MIN_CONFIG, remove the SKIP fr 69 # use the first MIN_CONFIG, remove the SKIP from the first
75 # DEFAULTS tag and add it to the second. Be ca 70 # DEFAULTS tag and add it to the second. Be careful, options
76 # may only be declared once per test or defaul 71 # may only be declared once per test or default. If you have
77 # the same option name under the same test or 72 # the same option name under the same test or as default
78 # ktest will fail to execute, and no tests wil 73 # ktest will fail to execute, and no tests will run.
79 # 74 #
80 # DEFAULTS OVERRIDE 75 # DEFAULTS OVERRIDE
81 # 76 #
82 # Options defined in the DEFAULTS section can 77 # Options defined in the DEFAULTS section can not be duplicated
83 # even if they are defined in two different DE 78 # even if they are defined in two different DEFAULT sections.
84 # This is done to catch mistakes where an opti 79 # This is done to catch mistakes where an option is added but
85 # the previous option was forgotten about and 80 # the previous option was forgotten about and not commented.
86 # 81 #
87 # The OVERRIDE keyword can be added to a secti 82 # The OVERRIDE keyword can be added to a section to allow this
88 # section to override other DEFAULT sections v 83 # section to override other DEFAULT sections values that have
89 # been defined previously. It will only overri 84 # been defined previously. It will only override options that
90 # have been defined before its use. Options de 85 # have been defined before its use. Options defined later
91 # in a non override section will still error. 86 # in a non override section will still error. The same option
92 # can not be defined in the same section even 87 # can not be defined in the same section even if that section
93 # is marked OVERRIDE. 88 # is marked OVERRIDE.
94 # 89 #
95 # 90 #
96 # 91 #
97 # Both TEST_START and DEFAULTS sections can al 92 # Both TEST_START and DEFAULTS sections can also have the IF keyword
98 # The value after the IF must evaluate into a 93 # The value after the IF must evaluate into a 0 or non 0 positive
99 # integer, and can use the config variables (e 94 # integer, and can use the config variables (explained below).
100 # 95 #
101 # DEFAULTS IF ${IS_X86_32} 96 # DEFAULTS IF ${IS_X86_32}
102 # 97 #
103 # The above will process the DEFAULTS section 98 # The above will process the DEFAULTS section if the config
104 # variable IS_X86_32 evaluates to a non zero p 99 # variable IS_X86_32 evaluates to a non zero positive integer
105 # otherwise if it evaluates to zero, it will a 100 # otherwise if it evaluates to zero, it will act the same
106 # as if the SKIP keyword was used. 101 # as if the SKIP keyword was used.
107 # 102 #
108 # The ELSE keyword can be used directly after 103 # The ELSE keyword can be used directly after a section with
109 # a IF statement. 104 # a IF statement.
110 # 105 #
111 # TEST_START IF ${RUN_NET_TESTS} 106 # TEST_START IF ${RUN_NET_TESTS}
112 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config- 107 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-network
113 # 108 #
114 # ELSE 109 # ELSE
115 # 110 #
116 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config- 111 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-normal
117 # 112 #
118 # 113 #
119 # The ELSE keyword can also contain an IF stat 114 # The ELSE keyword can also contain an IF statement to allow multiple
120 # if then else sections. But all the sections 115 # if then else sections. But all the sections must be either
121 # DEFAULT or TEST_START, they can not be a mix 116 # DEFAULT or TEST_START, they can not be a mixture.
122 # 117 #
123 # TEST_START IF ${RUN_NET_TESTS} 118 # TEST_START IF ${RUN_NET_TESTS}
124 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config- 119 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-network
125 # 120 #
126 # ELSE IF ${RUN_DISK_TESTS} 121 # ELSE IF ${RUN_DISK_TESTS}
127 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config- 122 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-tests
128 # 123 #
129 # ELSE IF ${RUN_CPU_TESTS} 124 # ELSE IF ${RUN_CPU_TESTS}
130 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config- 125 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-cpu
131 # 126 #
132 # ELSE 127 # ELSE
133 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config- 128 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-network
134 # 129 #
135 # The if statement may also have comparisons t 130 # The if statement may also have comparisons that will and for
136 # == and !=, strings may be used for both side 131 # == and !=, strings may be used for both sides.
137 # 132 #
138 # BOX_TYPE := x86_32 133 # BOX_TYPE := x86_32
139 # 134 #
140 # DEFAULTS IF ${BOX_TYPE} == x86_32 135 # DEFAULTS IF ${BOX_TYPE} == x86_32
141 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config- 136 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-32
142 # ELSE 137 # ELSE
143 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config- 138 # BUILD_TYPE = useconfig:${CONFIG_DIR}/config-64
144 # 139 #
145 # The DEFINED keyword can be used by the IF st 140 # The DEFINED keyword can be used by the IF statements too.
146 # It returns true if the given config variable 141 # It returns true if the given config variable or option has been defined
147 # or false otherwise. 142 # or false otherwise.
148 # 143 #
149 # 144 #
150 # DEFAULTS IF DEFINED USE_CC 145 # DEFAULTS IF DEFINED USE_CC
151 # CC := ${USE_CC} 146 # CC := ${USE_CC}
152 # ELSE 147 # ELSE
153 # CC := gcc 148 # CC := gcc
154 # 149 #
155 # 150 #
156 # As well as NOT DEFINED. 151 # As well as NOT DEFINED.
157 # 152 #
158 # DEFAULTS IF NOT DEFINED MAKE_CMD 153 # DEFAULTS IF NOT DEFINED MAKE_CMD
159 # MAKE_CMD := make ARCH=x86 154 # MAKE_CMD := make ARCH=x86
160 # 155 #
161 # 156 #
162 # And/or ops (&&,||) may also be used to make 157 # And/or ops (&&,||) may also be used to make complex conditionals.
163 # 158 #
164 # TEST_START IF (DEFINED ALL_TESTS || ${MYTEST 159 # TEST_START IF (DEFINED ALL_TESTS || ${MYTEST} == boottest) && ${MACHINE} == gandalf
165 # 160 #
166 # Notice the use of parentheses. Without any p 161 # Notice the use of parentheses. Without any parentheses the above would be
167 # processed the same as: 162 # processed the same as:
168 # 163 #
169 # TEST_START IF DEFINED ALL_TESTS || (${MYTEST 164 # TEST_START IF DEFINED ALL_TESTS || (${MYTEST} == boottest && ${MACHINE} == gandalf)
170 # 165 #
171 # 166 #
172 # 167 #
173 # INCLUDE file 168 # INCLUDE file
174 # 169 #
175 # The INCLUDE keyword may be used in DEFAULT s 170 # The INCLUDE keyword may be used in DEFAULT sections. This will
176 # read another config file and process that fi 171 # read another config file and process that file as well. The included
177 # file can include other files, add new test c 172 # file can include other files, add new test cases or default
178 # statements. Config variables will be passed 173 # statements. Config variables will be passed to these files and changes
179 # to config variables will be seen by top leve 174 # to config variables will be seen by top level config files. Including
180 # a file is processed just like the contents o 175 # a file is processed just like the contents of the file was cut and pasted
181 # into the top level file, except, that includ 176 # into the top level file, except, that include files that end with
182 # TEST_START sections will have that section e 177 # TEST_START sections will have that section ended at the end of
183 # the include file. That is, an included file 178 # the include file. That is, an included file is included followed
184 # by another DEFAULT keyword. 179 # by another DEFAULT keyword.
185 # 180 #
186 # Unlike other files referenced in this config 181 # Unlike other files referenced in this config, the file path does not need
187 # to be absolute. If the file does not start w 182 # to be absolute. If the file does not start with '/', then the directory
188 # that the current config file was located in 183 # that the current config file was located in is used. If no config by the
189 # given name is found there, then the current 184 # given name is found there, then the current directory is searched.
190 # 185 #
191 # INCLUDE myfile 186 # INCLUDE myfile
192 # DEFAULT 187 # DEFAULT
193 # 188 #
194 # is the same as: 189 # is the same as:
195 # 190 #
196 # INCLUDE myfile 191 # INCLUDE myfile
197 # 192 #
198 # Note, if the include file does not contain a 193 # Note, if the include file does not contain a full path, the file is
199 # searched first by the location of the origin 194 # searched first by the location of the original include file, and then
200 # by the location that ktest.pl was executed i 195 # by the location that ktest.pl was executed in.
201 # 196 #
202 197
203 #### Config variables #### 198 #### Config variables ####
204 # 199 #
205 # This config file can also contain "config va 200 # This config file can also contain "config variables".
206 # These are assigned with ":=" instead of the 201 # These are assigned with ":=" instead of the ktest option
207 # assignment "=". !! 202 # assigment "=".
208 # 203 #
209 # The difference between ktest options and con 204 # The difference between ktest options and config variables
210 # is that config variables can be used multipl 205 # is that config variables can be used multiple times,
211 # where each instance will override the previo 206 # where each instance will override the previous instance.
212 # And that they only live at time of processin 207 # And that they only live at time of processing this config.
213 # 208 #
214 # The advantage to config variables are that t 209 # The advantage to config variables are that they can be used
215 # by any option or any other config variables 210 # by any option or any other config variables to define thing
216 # that you may use over and over again in the 211 # that you may use over and over again in the options.
217 # 212 #
218 # For example: 213 # For example:
219 # 214 #
220 # USER := root 215 # USER := root
221 # TARGET := mybox 216 # TARGET := mybox
222 # TEST_CASE := ssh ${USER}@${TARGET} /path/to/ 217 # TEST_CASE := ssh ${USER}@${TARGET} /path/to/my/test
223 # 218 #
224 # TEST_START 219 # TEST_START
225 # MIN_CONFIG = config1 220 # MIN_CONFIG = config1
226 # TEST = ${TEST_CASE} 221 # TEST = ${TEST_CASE}
227 # 222 #
228 # TEST_START 223 # TEST_START
229 # MIN_CONFIG = config2 224 # MIN_CONFIG = config2
230 # TEST = ${TEST_CASE} 225 # TEST = ${TEST_CASE}
231 # 226 #
232 # TEST_CASE := ssh ${USER}@${TARGET} /path/to/ 227 # TEST_CASE := ssh ${USER}@${TARGET} /path/to/my/test2
233 # 228 #
234 # TEST_START 229 # TEST_START
235 # MIN_CONFIG = config1 230 # MIN_CONFIG = config1
236 # TEST = ${TEST_CASE} 231 # TEST = ${TEST_CASE}
237 # 232 #
238 # TEST_START 233 # TEST_START
239 # MIN_CONFIG = config2 234 # MIN_CONFIG = config2
240 # TEST = ${TEST_CASE} 235 # TEST = ${TEST_CASE}
241 # 236 #
242 # TEST_DIR := /home/me/test 237 # TEST_DIR := /home/me/test
243 # 238 #
244 # BUILD_DIR = ${TEST_DIR}/linux.git 239 # BUILD_DIR = ${TEST_DIR}/linux.git
245 # OUTPUT_DIR = ${TEST_DIR}/test 240 # OUTPUT_DIR = ${TEST_DIR}/test
246 # 241 #
247 # Note, the config variables are evaluated imm 242 # Note, the config variables are evaluated immediately, thus
248 # updating TARGET after TEST_CASE has been ass 243 # updating TARGET after TEST_CASE has been assigned does nothing
249 # to TEST_CASE. 244 # to TEST_CASE.
250 # 245 #
251 # As shown in the example, to evaluate a confi 246 # As shown in the example, to evaluate a config variable, you
252 # use the ${X} convention. Simple $X will not 247 # use the ${X} convention. Simple $X will not work.
253 # 248 #
254 # If the config variable does not exist, the $ 249 # If the config variable does not exist, the ${X} will not
255 # be evaluated. Thus: 250 # be evaluated. Thus:
256 # 251 #
257 # MAKE_CMD = PATH=/mypath:${PATH} make 252 # MAKE_CMD = PATH=/mypath:${PATH} make
258 # 253 #
259 # If PATH is not a config variable, then the $ 254 # If PATH is not a config variable, then the ${PATH} in
260 # the MAKE_CMD option will be evaluated by the 255 # the MAKE_CMD option will be evaluated by the shell when
261 # the MAKE_CMD option is passed into shell pro 256 # the MAKE_CMD option is passed into shell processing.
262 # <<
263 # Shell commands can also be inserted with the <<
264 # expression. Note, this is case sensitive, th <<
265 # will not work. <<
266 # <<
267 # HOSTNAME := ${shell hostname} <<
268 # DEFAULTS IF "${HOSTNAME}" == "frodo" <<
269 # <<
270 257
271 #### Using options in other options #### 258 #### Using options in other options ####
272 # 259 #
273 # Options that are defined in the config file 260 # Options that are defined in the config file may also be used
274 # by other options. All options are evaluated !! 261 # by other options. All options are evaulated at time of
275 # use (except that config variables are evalua 262 # use (except that config variables are evaluated at config
276 # processing time). 263 # processing time).
277 # 264 #
278 # If an ktest option is used within another op 265 # If an ktest option is used within another option, instead of
279 # typing it again in that option you can simpl 266 # typing it again in that option you can simply use the option
280 # just like you can config variables. 267 # just like you can config variables.
281 # 268 #
282 # MACHINE = mybox 269 # MACHINE = mybox
283 # 270 #
284 # TEST = ssh root@${MACHINE} /path/to/test 271 # TEST = ssh root@${MACHINE} /path/to/test
285 # 272 #
286 # The option will be used per test case. Thus: 273 # The option will be used per test case. Thus:
287 # 274 #
288 # TEST_TYPE = test 275 # TEST_TYPE = test
289 # TEST = ssh root@{MACHINE} 276 # TEST = ssh root@{MACHINE}
290 # 277 #
291 # TEST_START 278 # TEST_START
292 # MACHINE = box1 279 # MACHINE = box1
293 # 280 #
294 # TEST_START 281 # TEST_START
295 # MACHINE = box2 282 # MACHINE = box2
296 # 283 #
297 # For both test cases, MACHINE will be evaluat 284 # For both test cases, MACHINE will be evaluated at the time
298 # of the test case. The first test will run ss 285 # of the test case. The first test will run ssh root@box1
299 # and the second will run ssh root@box2. 286 # and the second will run ssh root@box2.
300 287
301 #### Mandatory Default Options #### 288 #### Mandatory Default Options ####
302 289
303 # These options must be in the default section 290 # These options must be in the default section, although most
304 # may be overridden by test options. 291 # may be overridden by test options.
305 292
306 # The machine hostname that you will test 293 # The machine hostname that you will test
307 #MACHINE = target 294 #MACHINE = target
308 295
309 # The box is expected to have ssh on normal bo 296 # The box is expected to have ssh on normal bootup, provide the user
310 # (most likely root, since you need privilege 297 # (most likely root, since you need privileged operations)
311 #SSH_USER = root 298 #SSH_USER = root
312 299
313 # The directory that contains the Linux source 300 # The directory that contains the Linux source code
314 #BUILD_DIR = /home/test/linux.git 301 #BUILD_DIR = /home/test/linux.git
315 302
316 # The directory that the objects will be built 303 # The directory that the objects will be built
317 # (can not be same as BUILD_DIR) 304 # (can not be same as BUILD_DIR)
318 #OUTPUT_DIR = /home/test/build/target 305 #OUTPUT_DIR = /home/test/build/target
319 306
320 # The location of the compiled file to copy to 307 # The location of the compiled file to copy to the target
321 # (relative to OUTPUT_DIR) 308 # (relative to OUTPUT_DIR)
322 #BUILD_TARGET = arch/x86/boot/bzImage 309 #BUILD_TARGET = arch/x86/boot/bzImage
323 310
324 # The place to put your image on the test mach 311 # The place to put your image on the test machine
325 #TARGET_IMAGE = /boot/vmlinuz-test 312 #TARGET_IMAGE = /boot/vmlinuz-test
326 313
327 # A script or command to reboot the box 314 # A script or command to reboot the box
328 # 315 #
329 # Here is a digital loggers power switch examp 316 # Here is a digital loggers power switch example
330 #POWER_CYCLE = wget --no-proxy -O /dev/null -q 317 #POWER_CYCLE = wget --no-proxy -O /dev/null -q --auth-no-challenge 'http://admin:admin@power/outlet?5=CCL'
331 # 318 #
332 # Here is an example to reboot a virtual box o 319 # Here is an example to reboot a virtual box on the current host
333 # with the name "Guest". 320 # with the name "Guest".
334 #POWER_CYCLE = virsh destroy Guest; sleep 5; v 321 #POWER_CYCLE = virsh destroy Guest; sleep 5; virsh start Guest
335 322
336 # The script or command that reads the console 323 # The script or command that reads the console
337 # 324 #
338 # If you use ttywatch server, something like 325 # If you use ttywatch server, something like the following would work.
339 #CONSOLE = nc -d localhost 3001 326 #CONSOLE = nc -d localhost 3001
340 # 327 #
341 # For a virtual machine with guest name "Guest 328 # For a virtual machine with guest name "Guest".
342 #CONSOLE = virsh console Guest 329 #CONSOLE = virsh console Guest
343 330
344 # Signal to send to kill console. <<
345 # ktest.pl will create a child process to moni <<
346 # When the console is finished, ktest will kil <<
347 # with this signal. <<
348 # (default INT) <<
349 #CLOSE_CONSOLE_SIGNAL = HUP <<
350 <<
351 # Required version ending to differentiate the 331 # Required version ending to differentiate the test
352 # from other linux builds on the system. 332 # from other linux builds on the system.
353 #LOCALVERSION = -test 333 #LOCALVERSION = -test
354 334
355 # For REBOOT_TYPE = grub2, you must specify wh 335 # For REBOOT_TYPE = grub2, you must specify where the grub.cfg
356 # file is. This is the file that is searched t 336 # file is. This is the file that is searched to find the menu
357 # option to boot to with GRUB_REBOOT 337 # option to boot to with GRUB_REBOOT
358 #GRUB_FILE = /boot/grub2/grub.cfg 338 #GRUB_FILE = /boot/grub2/grub.cfg
359 339
360 # The tool for REBOOT_TYPE = grub2 or grub2bls !! 340 # The tool for REBOOT_TYPE = grub2 to set the next reboot kernel
361 # to boot into (one shot mode). 341 # to boot into (one shot mode).
362 # (default grub2_reboot) 342 # (default grub2_reboot)
363 #GRUB_REBOOT = grub2_reboot 343 #GRUB_REBOOT = grub2_reboot
364 344
365 # The grub title name for the test kernel to b 345 # The grub title name for the test kernel to boot
366 # (Only mandatory if REBOOT_TYPE = grub or gru !! 346 # (Only mandatory if REBOOT_TYPE = grub or grub2)
367 # 347 #
368 # Note, ktest.pl will not update the grub menu 348 # Note, ktest.pl will not update the grub menu.lst, you need to
369 # manually add an option for the test. ktest.p 349 # manually add an option for the test. ktest.pl will search
370 # the grub menu.lst for this option to find wh 350 # the grub menu.lst for this option to find what kernel to
371 # reboot into. 351 # reboot into.
372 # 352 #
373 # For example, if in the /boot/grub/menu.lst t 353 # For example, if in the /boot/grub/menu.lst the test kernel title has:
374 # title Test Kernel 354 # title Test Kernel
375 # kernel vmlinuz-test 355 # kernel vmlinuz-test
376 # 356 #
377 # For grub2, a search of top level "menuentry" 357 # For grub2, a search of top level "menuentry"s are done. No
378 # submenu is searched. The menu is found by se 358 # submenu is searched. The menu is found by searching for the
379 # contents of GRUB_MENU in the line that start 359 # contents of GRUB_MENU in the line that starts with "menuentry".
380 # You may want to include the quotes around th 360 # You may want to include the quotes around the option. For example:
381 # for: menuentry 'Test Kernel' 361 # for: menuentry 'Test Kernel'
382 # do a: GRUB_MENU = 'Test Kernel' 362 # do a: GRUB_MENU = 'Test Kernel'
383 # For customizing, add your entry in /etc/grub 363 # For customizing, add your entry in /etc/grub.d/40_custom.
384 # 364 #
385 # For grub2bls, a search of "title"s are done. <<
386 # by searching for the contents of GRUB_MENU i <<
387 # with "title". <<
388 # <<
389 #GRUB_MENU = Test Kernel 365 #GRUB_MENU = Test Kernel
390 366
391 # For REBOOT_TYPE = syslinux, the name of the 367 # For REBOOT_TYPE = syslinux, the name of the syslinux executable
392 # (on the target) to use to set up the next re 368 # (on the target) to use to set up the next reboot to boot the
393 # test kernel. 369 # test kernel.
394 # (default extlinux) 370 # (default extlinux)
395 #SYSLINUX = syslinux 371 #SYSLINUX = syslinux
396 372
397 # For REBOOT_TYPE = syslinux, the path that is 373 # For REBOOT_TYPE = syslinux, the path that is passed to to the
398 # syslinux command where syslinux is installed 374 # syslinux command where syslinux is installed.
399 # (default /boot/extlinux) 375 # (default /boot/extlinux)
400 #SYSLINUX_PATH = /boot/syslinux 376 #SYSLINUX_PATH = /boot/syslinux
401 377
402 # For REBOOT_TYPE = syslinux, the syslinux lab 378 # For REBOOT_TYPE = syslinux, the syslinux label that references the
403 # test kernel in the syslinux config file. 379 # test kernel in the syslinux config file.
404 # (default undefined) 380 # (default undefined)
405 #SYSLINUX_LABEL = "test-kernel" 381 #SYSLINUX_LABEL = "test-kernel"
406 382
407 # A script to reboot the target into the test 383 # A script to reboot the target into the test kernel
408 # This and SWITCH_TO_TEST are about the same, 384 # This and SWITCH_TO_TEST are about the same, except
409 # SWITCH_TO_TEST is run even for REBOOT_TYPE = 385 # SWITCH_TO_TEST is run even for REBOOT_TYPE = grub.
410 # This may be left undefined. 386 # This may be left undefined.
411 # (default undefined) 387 # (default undefined)
412 #REBOOT_SCRIPT = 388 #REBOOT_SCRIPT =
413 389
414 #### Optional Config Options (all have default 390 #### Optional Config Options (all have defaults) ####
415 391
416 # Email options for receiving notifications. U <<
417 # the specified mailer prior to using this fea <<
418 # <<
419 # (default undefined) <<
420 #MAILTO = <<
421 # <<
422 # Supported mailers: sendmail, mail, mailx <<
423 # (default sendmail) <<
424 #MAILER = sendmail <<
425 # <<
426 # The executable to run <<
427 # (default: for sendmail "/usr/sbin/sendmail", <<
428 #MAIL_EXEC = /usr/sbin/sendmail <<
429 # <<
430 # The command used to send mail, which uses th <<
431 # can be modified. By default if the mailer is <<
432 # MAIL_COMMAND = echo \'Subject: $SUBJECT\n\n <<
433 # For mail or mailx: <<
434 # MAIL_COMMAND = "$MAIL_PATH/$MAILER -s \'$SU <<
435 # ktest.pl will do the substitution for MAIL_P <<
436 # it sends the mail if "$FOO" format is use <<
437 # then the substitutions will occur at the <<
438 # But note, MAIL_PATH and MAILER require be <<
439 # ${MAIL_PATH} or ${MAILER} are used, but <<
440 #MAIL_COMMAND = echo \'Subject: $SUBJECT\n\n$M <<
441 # <<
442 # Errors are defined as those would terminate <<
443 # (default 1) <<
444 #EMAIL_ON_ERROR = 1 <<
445 # (default 1) <<
446 #EMAIL_WHEN_FINISHED = 1 <<
447 # (default 0) <<
448 #EMAIL_WHEN_STARTED = 1 <<
449 # <<
450 # Users can cancel the test by Ctrl^C <<
451 # (default 0) <<
452 #EMAIL_WHEN_CANCELED = 1 <<
453 # <<
454 # If a test ends with an error and EMAIL_ON_ER <<
455 # as a LOG_FILE is defined, then the log of th <<
456 # be included in the email that is sent. <<
457 # It is possible that the log may be very larg <<
458 # only the last amount of the log should be se <<
459 # much of the log is sent, set MAIL_MAX_SIZE. <<
460 # size in bytes of the last portion of the log <<
461 # test file. That is, if this is set to 100000 <<
462 # last 100 thousand bytes of the log file will <<
463 # the email. <<
464 # (default undef) <<
465 #MAIL_MAX_SIZE = 1000000 <<
466 <<
467 # Start a test setup. If you leave this off, a 392 # Start a test setup. If you leave this off, all options
468 # will be default and the test will run once. 393 # will be default and the test will run once.
469 # This is a label and not really an option (it 394 # This is a label and not really an option (it takes no value).
470 # You can append ITERATE and a number after it 395 # You can append ITERATE and a number after it to iterate the
471 # test a number of times, or SKIP to ignore th 396 # test a number of times, or SKIP to ignore this test.
472 # 397 #
473 #TEST_START 398 #TEST_START
474 #TEST_START ITERATE 5 399 #TEST_START ITERATE 5
475 #TEST_START SKIP 400 #TEST_START SKIP
476 401
477 # Have the following options as default again. 402 # Have the following options as default again. Used after tests
478 # have already been defined by TEST_START. Opt 403 # have already been defined by TEST_START. Optionally, you can
479 # just define all default options before the f 404 # just define all default options before the first TEST_START
480 # and you do not need this option. 405 # and you do not need this option.
481 # 406 #
482 # This is a label and not really an option (it 407 # This is a label and not really an option (it takes no value).
483 # You can append SKIP to this label and the op 408 # You can append SKIP to this label and the options within this
484 # section will be ignored. 409 # section will be ignored.
485 # 410 #
486 # DEFAULTS 411 # DEFAULTS
487 # DEFAULTS SKIP 412 # DEFAULTS SKIP
488 413
489 # If you want to execute some command before t 414 # If you want to execute some command before the first test runs
490 # you can set this option. Note, it can be set 415 # you can set this option. Note, it can be set as a default option
491 # or an option in the first test case. All oth 416 # or an option in the first test case. All other test cases will
492 # ignore it. If both the default and first tes 417 # ignore it. If both the default and first test have this option
493 # set, then the first test will take precedenc 418 # set, then the first test will take precedence.
494 # 419 #
495 # default (undefined) 420 # default (undefined)
496 #PRE_KTEST = ${SSH} ~/set_up_test 421 #PRE_KTEST = ${SSH} ~/set_up_test
497 422
498 # If you want to execute some command after al 423 # If you want to execute some command after all the tests have
499 # completed, you can set this option. Note, it 424 # completed, you can set this option. Note, it can be set as a
500 # default or any test case can override it. If 425 # default or any test case can override it. If multiple test cases
501 # set this option, then the last test case tha 426 # set this option, then the last test case that set it will take
502 # precedence 427 # precedence
503 # 428 #
504 # default (undefined) 429 # default (undefined)
505 #POST_KTEST = ${SSH} ~/dismantle_test 430 #POST_KTEST = ${SSH} ~/dismantle_test
506 431
507 # If you want to remove the kernel entry in Bo <<
508 # environment, use kernel-install command. <<
509 # Here's the example: <<
510 #POST_KTEST = ssh root@Test "/usr/bin/kernel-i <<
511 <<
512 # The default test type (default test) 432 # The default test type (default test)
513 # The test types may be: 433 # The test types may be:
514 # build - only build the kernel, do nothin 434 # build - only build the kernel, do nothing else
515 # install - build and install, but do nothin 435 # install - build and install, but do nothing else (does not reboot)
516 # boot - build, install, and boot the ker 436 # boot - build, install, and boot the kernel
517 # test - build, boot and if TEST is set, 437 # test - build, boot and if TEST is set, run the test script
518 # (If TEST is not set, it defaults ba 438 # (If TEST is not set, it defaults back to boot)
519 # bisect - Perform a bisect on the kernel (s 439 # bisect - Perform a bisect on the kernel (see BISECT_TYPE below)
520 # patchcheck - Do a test on a series of comm 440 # patchcheck - Do a test on a series of commits in git (see PATCHCHECK below)
521 #TEST_TYPE = test 441 #TEST_TYPE = test
522 442
523 # Test to run if there is a successful boot an 443 # Test to run if there is a successful boot and TEST_TYPE is test.
524 # Must exit with 0 on success and non zero on 444 # Must exit with 0 on success and non zero on error
525 # default (undefined) 445 # default (undefined)
526 #TEST = ssh user@machine /root/run_test 446 #TEST = ssh user@machine /root/run_test
527 447
528 # The build type is any make config type or sp 448 # The build type is any make config type or special command
529 # (default oldconfig) !! 449 # (default randconfig)
530 # nobuild - skip the clean and build step 450 # nobuild - skip the clean and build step
531 # useconfig:/path/to/config - use the given 451 # useconfig:/path/to/config - use the given config and run
532 # oldconfig on it. 452 # oldconfig on it.
533 # This option is ignored if TEST_TYPE is patch 453 # This option is ignored if TEST_TYPE is patchcheck or bisect
534 #BUILD_TYPE = randconfig 454 #BUILD_TYPE = randconfig
535 455
536 # The make command (default make) 456 # The make command (default make)
537 # If you are building a 32bit x86 on a 64 bit 457 # If you are building a 32bit x86 on a 64 bit host
538 #MAKE_CMD = CC=i386-gcc AS=i386-as make ARCH=i 458 #MAKE_CMD = CC=i386-gcc AS=i386-as make ARCH=i386
539 459
540 # Any build options for the make of the kernel 460 # Any build options for the make of the kernel (not for other makes, like configs)
541 # (default "") 461 # (default "")
542 #BUILD_OPTIONS = -j20 462 #BUILD_OPTIONS = -j20
543 463
544 # If you need to do some special handling befo 464 # If you need to do some special handling before installing
545 # you can add a script with this option. 465 # you can add a script with this option.
546 # The environment variable KERNEL_VERSION will 466 # The environment variable KERNEL_VERSION will be set to the
547 # kernel version that is used. 467 # kernel version that is used.
548 # 468 #
549 # default (undefined) 469 # default (undefined)
550 #PRE_INSTALL = ssh user@target rm -rf '/lib/mo 470 #PRE_INSTALL = ssh user@target rm -rf '/lib/modules/*-test*'
551 471
552 # If you need an initrd, you can add a script 472 # If you need an initrd, you can add a script or code here to install
553 # it. The environment variable KERNEL_VERSION 473 # it. The environment variable KERNEL_VERSION will be set to the
554 # kernel version that is used. Remember to add 474 # kernel version that is used. Remember to add the initrd line
555 # to your grub menu.lst file. 475 # to your grub menu.lst file.
556 # 476 #
557 # Here's a couple of examples to use: 477 # Here's a couple of examples to use:
558 #POST_INSTALL = ssh user@target /sbin/mkinitrd 478 #POST_INSTALL = ssh user@target /sbin/mkinitrd --allow-missing -f /boot/initramfs-test.img $KERNEL_VERSION
559 # 479 #
560 # or on some systems: 480 # or on some systems:
561 #POST_INSTALL = ssh user@target /sbin/dracut - 481 #POST_INSTALL = ssh user@target /sbin/dracut -f /boot/initramfs-test.img $KERNEL_VERSION
562 482
563 # If you want to add the kernel entry in Boot <<
564 # environment, use kernel-install command. <<
565 # Here's the example: <<
566 #POST_INSTALL = ssh root@Test "/usr/bin/kernel <<
567 <<
568 # If for some reason you just want to boot the 483 # If for some reason you just want to boot the kernel and you do not
569 # want the test to install anything new. For e 484 # want the test to install anything new. For example, you may just want
570 # to boot test the same kernel over and over a 485 # to boot test the same kernel over and over and do not want to go through
571 # the hassle of installing anything, you can s 486 # the hassle of installing anything, you can set this option to 1
572 # (default 0) 487 # (default 0)
573 #NO_INSTALL = 1 488 #NO_INSTALL = 1
574 489
575 # If there is a command that you want to run b 490 # If there is a command that you want to run before the individual test
576 # case executes, then you can set this option 491 # case executes, then you can set this option
577 # 492 #
578 # default (undefined) 493 # default (undefined)
579 #PRE_TEST = ${SSH} reboot_to_special_kernel 494 #PRE_TEST = ${SSH} reboot_to_special_kernel
580 495
581 # To kill the entire test if PRE_TEST is defin <<
582 # to 1. <<
583 # (default 0) <<
584 #PRE_TEST_DIE = 1 <<
585 <<
586 # If there is a command you want to run after 496 # If there is a command you want to run after the individual test case
587 # completes, then you can set this option. 497 # completes, then you can set this option.
588 # 498 #
589 # default (undefined) 499 # default (undefined)
590 #POST_TEST = cd ${BUILD_DIR}; git reset --hard 500 #POST_TEST = cd ${BUILD_DIR}; git reset --hard
591 501
592 # If there is a script that you require to run 502 # If there is a script that you require to run before the build is done
593 # you can specify it with PRE_BUILD. 503 # you can specify it with PRE_BUILD.
594 # 504 #
595 # One example may be if you must add a tempora 505 # One example may be if you must add a temporary patch to the build to
596 # fix a unrelated bug to perform a patchcheck 506 # fix a unrelated bug to perform a patchcheck test. This will apply the
597 # patch before each build that is made. Use th 507 # patch before each build that is made. Use the POST_BUILD to do a git reset --hard
598 # to remove the patch. 508 # to remove the patch.
599 # 509 #
600 # (default undef) 510 # (default undef)
601 #PRE_BUILD = cd ${BUILD_DIR} && patch -p1 < /t 511 #PRE_BUILD = cd ${BUILD_DIR} && patch -p1 < /tmp/temp.patch
602 512
603 # To specify if the test should fail if the PR 513 # To specify if the test should fail if the PRE_BUILD fails,
604 # PRE_BUILD_DIE needs to be set to 1. Otherwis 514 # PRE_BUILD_DIE needs to be set to 1. Otherwise the PRE_BUILD
605 # result is ignored. 515 # result is ignored.
606 # (default 0) 516 # (default 0)
607 # PRE_BUILD_DIE = 1 517 # PRE_BUILD_DIE = 1
608 518
609 # If there is a script that should run after t 519 # If there is a script that should run after the build is done
610 # you can specify it with POST_BUILD. 520 # you can specify it with POST_BUILD.
611 # 521 #
612 # As the example in PRE_BUILD, POST_BUILD can 522 # As the example in PRE_BUILD, POST_BUILD can be used to reset modifications
613 # made by the PRE_BUILD. 523 # made by the PRE_BUILD.
614 # 524 #
615 # (default undef) 525 # (default undef)
616 #POST_BUILD = cd ${BUILD_DIR} && git reset --h 526 #POST_BUILD = cd ${BUILD_DIR} && git reset --hard
617 527
618 # To specify if the test should fail if the PO 528 # To specify if the test should fail if the POST_BUILD fails,
619 # POST_BUILD_DIE needs to be set to 1. Otherwi 529 # POST_BUILD_DIE needs to be set to 1. Otherwise the POST_BUILD
620 # result is ignored. 530 # result is ignored.
621 # (default 0) 531 # (default 0)
622 #POST_BUILD_DIE = 1 532 #POST_BUILD_DIE = 1
623 533
624 # Way to reboot the box to the test kernel. 534 # Way to reboot the box to the test kernel.
625 # Only valid options so far are "grub", "grub2 535 # Only valid options so far are "grub", "grub2", "syslinux" and "script"
626 # (default grub) 536 # (default grub)
627 # If you specify grub, it will assume grub ver 537 # If you specify grub, it will assume grub version 1
628 # and will search in /boot/grub/menu.lst for t 538 # and will search in /boot/grub/menu.lst for the title $GRUB_MENU
629 # and select that target to reboot to the kern 539 # and select that target to reboot to the kernel. If this is not
630 # your setup, then specify "script" and have a 540 # your setup, then specify "script" and have a command or script
631 # specified in REBOOT_SCRIPT to boot to the ta 541 # specified in REBOOT_SCRIPT to boot to the target.
632 # 542 #
633 # For REBOOT_TYPE = grub2, you must define bot 543 # For REBOOT_TYPE = grub2, you must define both GRUB_MENU and
634 # GRUB_FILE. 544 # GRUB_FILE.
635 # 545 #
636 # For REBOOT_TYPE = grub2bls, you must define <<
637 # <<
638 # For REBOOT_TYPE = syslinux, you must define 546 # For REBOOT_TYPE = syslinux, you must define SYSLINUX_LABEL, and
639 # perhaps modify SYSLINUX (default extlinux) a 547 # perhaps modify SYSLINUX (default extlinux) and SYSLINUX_PATH
640 # (default /boot/extlinux) 548 # (default /boot/extlinux)
641 # 549 #
642 # The entry in /boot/grub/menu.lst must be ent 550 # The entry in /boot/grub/menu.lst must be entered in manually.
643 # The test will not modify that file. 551 # The test will not modify that file.
644 #REBOOT_TYPE = grub 552 #REBOOT_TYPE = grub
645 553
646 # If you are using a machine that doesn't boot 554 # If you are using a machine that doesn't boot with grub, and
647 # perhaps gets its kernel from a remote server 555 # perhaps gets its kernel from a remote server (tftp), then
648 # you can use this option to update the target 556 # you can use this option to update the target image with the
649 # test image. 557 # test image.
650 # 558 #
651 # You could also do the same with POST_INSTALL 559 # You could also do the same with POST_INSTALL, but the difference
652 # between that option and this option is that 560 # between that option and this option is that POST_INSTALL runs
653 # after the install, where this one runs just 561 # after the install, where this one runs just before a reboot.
654 # (default undefined) 562 # (default undefined)
655 #SWITCH_TO_TEST = cp ${OUTPUT_DIR}/${BUILD_TAR 563 #SWITCH_TO_TEST = cp ${OUTPUT_DIR}/${BUILD_TARGET} ${TARGET_IMAGE}
656 564
657 # If you are using a machine that doesn't boot 565 # If you are using a machine that doesn't boot with grub, and
658 # perhaps gets its kernel from a remote server 566 # perhaps gets its kernel from a remote server (tftp), then
659 # you can use this option to update the target 567 # you can use this option to update the target image with the
660 # the known good image to reboot safely back i 568 # the known good image to reboot safely back into.
661 # 569 #
662 # This option holds a command that will execut 570 # This option holds a command that will execute before needing
663 # to reboot to a good known image. 571 # to reboot to a good known image.
664 # (default undefined) 572 # (default undefined)
665 #SWITCH_TO_GOOD = ssh ${SSH_USER}/${MACHINE} c 573 #SWITCH_TO_GOOD = ssh ${SSH_USER}/${MACHINE} cp good_image ${TARGET_IMAGE}
666 574
667 # The min config that is needed to build for t 575 # The min config that is needed to build for the machine
668 # A nice way to create this is with the follow 576 # A nice way to create this is with the following:
669 # 577 #
670 # $ ssh target 578 # $ ssh target
671 # $ lsmod > mymods 579 # $ lsmod > mymods
672 # $ scp mymods host:/tmp 580 # $ scp mymods host:/tmp
673 # $ exit 581 # $ exit
674 # $ cd linux.git 582 # $ cd linux.git
675 # $ rm .config 583 # $ rm .config
676 # $ make LSMOD=mymods localyesconfig 584 # $ make LSMOD=mymods localyesconfig
677 # $ grep '^CONFIG' .config > /home/test/conf 585 # $ grep '^CONFIG' .config > /home/test/config-min
678 # 586 #
679 # If you want even less configs: 587 # If you want even less configs:
680 # 588 #
681 # log in directly to target (do not ssh) 589 # log in directly to target (do not ssh)
682 # 590 #
683 # $ su 591 # $ su
684 # # lsmod | cut -d' ' -f1 | xargs rmmod 592 # # lsmod | cut -d' ' -f1 | xargs rmmod
685 # 593 #
686 # repeat the above several times 594 # repeat the above several times
687 # 595 #
688 # # lsmod > mymods 596 # # lsmod > mymods
689 # # reboot 597 # # reboot
690 # 598 #
691 # May need to reboot to get your network back 599 # May need to reboot to get your network back to copy the mymods
692 # to the host, and then remove the previous .c 600 # to the host, and then remove the previous .config and run the
693 # localyesconfig again. The CONFIG_MIN generat 601 # localyesconfig again. The CONFIG_MIN generated like this will
694 # not guarantee network activity to the box so 602 # not guarantee network activity to the box so the TEST_TYPE of
695 # test may fail. 603 # test may fail.
696 # 604 #
697 # You might also want to set: 605 # You might also want to set:
698 # CONFIG_CMDLINE="<your options here>" 606 # CONFIG_CMDLINE="<your options here>"
699 # randconfig may set the above and override y 607 # randconfig may set the above and override your real command
700 # line options. 608 # line options.
701 # (default undefined) 609 # (default undefined)
702 #MIN_CONFIG = /home/test/config-min 610 #MIN_CONFIG = /home/test/config-min
703 611
704 # Sometimes there's options that just break th 612 # Sometimes there's options that just break the boot and
705 # you do not care about. Here are a few: 613 # you do not care about. Here are a few:
706 # # CONFIG_STAGING is not set 614 # # CONFIG_STAGING is not set
707 # Staging drivers are horrible, and can break 615 # Staging drivers are horrible, and can break the build.
708 # # CONFIG_SCSI_DEBUG is not set 616 # # CONFIG_SCSI_DEBUG is not set
709 # SCSI_DEBUG may change your root partition 617 # SCSI_DEBUG may change your root partition
710 # # CONFIG_KGDB_SERIAL_CONSOLE is not set 618 # # CONFIG_KGDB_SERIAL_CONSOLE is not set
711 # KGDB may cause oops waiting for a connectio 619 # KGDB may cause oops waiting for a connection that's not there.
712 # This option points to the file containing co 620 # This option points to the file containing config options that will be prepended
713 # to the MIN_CONFIG (or be the MIN_CONFIG if i 621 # to the MIN_CONFIG (or be the MIN_CONFIG if it is not set)
714 # 622 #
715 # Note, config options in MIN_CONFIG will over 623 # Note, config options in MIN_CONFIG will override these options.
716 # 624 #
717 # (default undefined) 625 # (default undefined)
718 #ADD_CONFIG = /home/test/config-broken 626 #ADD_CONFIG = /home/test/config-broken
719 627
720 # The location on the host where to write temp 628 # The location on the host where to write temp files
721 # (default /tmp/ktest/${MACHINE}) 629 # (default /tmp/ktest/${MACHINE})
722 #TMP_DIR = /tmp/ktest/${MACHINE} 630 #TMP_DIR = /tmp/ktest/${MACHINE}
723 631
724 # Optional log file to write the status (recom 632 # Optional log file to write the status (recommended)
725 # Note, this is a DEFAULT section only option 633 # Note, this is a DEFAULT section only option.
726 # (default undefined) 634 # (default undefined)
727 #LOG_FILE = /home/test/logfiles/target.log 635 #LOG_FILE = /home/test/logfiles/target.log
728 636
729 # Remove old logfile if it exists before start 637 # Remove old logfile if it exists before starting all tests.
730 # Note, this is a DEFAULT section only option 638 # Note, this is a DEFAULT section only option.
731 # (default 0) 639 # (default 0)
732 #CLEAR_LOG = 0 640 #CLEAR_LOG = 0
733 641
734 # Line to define a successful boot up in conso 642 # Line to define a successful boot up in console output.
735 # This is what the line contains, not the enti 643 # This is what the line contains, not the entire line. If you need
736 # the entire line to match, then use regular e !! 644 # the entire line to match, then use regural expression syntax like:
737 # (do not add any quotes around it) 645 # (do not add any quotes around it)
738 # 646 #
739 # SUCCESS_LINE = ^MyBox Login:$ 647 # SUCCESS_LINE = ^MyBox Login:$
740 # 648 #
741 # (default "login:") 649 # (default "login:")
742 #SUCCESS_LINE = login: 650 #SUCCESS_LINE = login:
743 651
744 # To speed up between reboots, defining a line 652 # To speed up between reboots, defining a line that the
745 # default kernel produces that represents that 653 # default kernel produces that represents that the default
746 # kernel has successfully booted and can be us 654 # kernel has successfully booted and can be used to pass
747 # a new test kernel to it. Otherwise ktest.pl 655 # a new test kernel to it. Otherwise ktest.pl will wait till
748 # SLEEP_TIME to continue. 656 # SLEEP_TIME to continue.
749 # (default undefined) 657 # (default undefined)
750 #REBOOT_SUCCESS_LINE = login: 658 #REBOOT_SUCCESS_LINE = login:
751 659
752 # In case the console constantly fills the scr 660 # In case the console constantly fills the screen, having
753 # a specified time to stop the test after succ 661 # a specified time to stop the test after success is recommended.
754 # (in seconds) 662 # (in seconds)
755 # (default 10) 663 # (default 10)
756 #STOP_AFTER_SUCCESS = 10 664 #STOP_AFTER_SUCCESS = 10
757 665
758 # In case the console constantly fills the scr 666 # In case the console constantly fills the screen, having
759 # a specified time to stop the test after fail 667 # a specified time to stop the test after failure is recommended.
760 # (in seconds) 668 # (in seconds)
761 # (default 60) 669 # (default 60)
762 #STOP_AFTER_FAILURE = 60 670 #STOP_AFTER_FAILURE = 60
763 671
764 # In case the console constantly fills the scr 672 # In case the console constantly fills the screen, having
765 # a specified time to stop the test if it neve 673 # a specified time to stop the test if it never succeeds nor fails
766 # is recommended. 674 # is recommended.
767 # Note: this is ignored if a success or failur 675 # Note: this is ignored if a success or failure is detected.
768 # (in seconds) 676 # (in seconds)
769 # (default 600, -1 is to never stop) 677 # (default 600, -1 is to never stop)
770 #STOP_TEST_AFTER = 600 678 #STOP_TEST_AFTER = 600
771 679
772 # Stop testing if a build fails. If set, the s 680 # Stop testing if a build fails. If set, the script will end if
773 # a failure is detected, otherwise it will sav 681 # a failure is detected, otherwise it will save off the .config,
774 # dmesg and bootlog in a directory called 682 # dmesg and bootlog in a directory called
775 # MACHINE-TEST_TYPE_BUILD_TYPE-fail-yyyymmddhh 683 # MACHINE-TEST_TYPE_BUILD_TYPE-fail-yyyymmddhhmmss
776 # if the STORE_FAILURES directory is set. 684 # if the STORE_FAILURES directory is set.
777 # (default 1) 685 # (default 1)
778 # Note, even if this is set to zero, there are 686 # Note, even if this is set to zero, there are some errors that still
779 # stop the tests. 687 # stop the tests.
780 #DIE_ON_FAILURE = 1 688 #DIE_ON_FAILURE = 1
781 689
782 # Directory to store failure directories on fa 690 # Directory to store failure directories on failure. If this is not
783 # set, DIE_ON_FAILURE=0 will not save off the 691 # set, DIE_ON_FAILURE=0 will not save off the .config, dmesg and
784 # bootlog. This option is ignored if DIE_ON_FA 692 # bootlog. This option is ignored if DIE_ON_FAILURE is not set.
785 # (default undefined) 693 # (default undefined)
786 #STORE_FAILURES = /home/test/failures 694 #STORE_FAILURES = /home/test/failures
787 695
788 # Directory to store success directories on su 696 # Directory to store success directories on success. If this is not
789 # set, the .config, dmesg and bootlog will not 697 # set, the .config, dmesg and bootlog will not be saved if a
790 # test succeeds. 698 # test succeeds.
791 # (default undefined) 699 # (default undefined)
792 #STORE_SUCCESSES = /home/test/successes 700 #STORE_SUCCESSES = /home/test/successes
793 701
794 # Build without doing a make mrproper, or remo 702 # Build without doing a make mrproper, or removing .config
795 # (default 0) 703 # (default 0)
796 #BUILD_NOCLEAN = 0 704 #BUILD_NOCLEAN = 0
797 705
798 # As the test reads the console, after it hits 706 # As the test reads the console, after it hits the SUCCESS_LINE
799 # the time it waits for the monitor to settle 707 # the time it waits for the monitor to settle down between reads
800 # can usually be lowered. 708 # can usually be lowered.
801 # (in seconds) (default 1) 709 # (in seconds) (default 1)
802 #BOOTED_TIMEOUT = 1 710 #BOOTED_TIMEOUT = 1
803 711
804 # The timeout in seconds when we consider the 712 # The timeout in seconds when we consider the box hung after
805 # the console stop producing output. Be sure t 713 # the console stop producing output. Be sure to leave enough
806 # time here to get pass a reboot. Some machine 714 # time here to get pass a reboot. Some machines may not produce
807 # any console output for a long time during a 715 # any console output for a long time during a reboot. You do
808 # not want the test to fail just because the s 716 # not want the test to fail just because the system was in
809 # the process of rebooting to the test kernel. 717 # the process of rebooting to the test kernel.
810 # (default 120) 718 # (default 120)
811 #TIMEOUT = 120 719 #TIMEOUT = 120
812 720
813 # The timeout in seconds when to test if the b <<
814 # or not. Before issuing the reboot command, a <<
815 # is attempted to see if the target machine is <<
816 # If the target does not connect within this t <<
817 # is issued instead of a reboot. <<
818 # CONNECT_TIMEOUT = 25 <<
819 <<
820 # The timeout in seconds for how long to wait <<
821 # to timeout. If not defined, it will let it g <<
822 # (default undefined) <<
823 #RUN_TIMEOUT = 600 <<
824 <<
825 # In between tests, a reboot of the box may oc 721 # In between tests, a reboot of the box may occur, and this
826 # is the time to wait for the console after it 722 # is the time to wait for the console after it stops producing
827 # output. Some machines may not produce a larg 723 # output. Some machines may not produce a large lag on reboot
828 # so this should accommodate it. 724 # so this should accommodate it.
829 # The difference between this and TIMEOUT, is 725 # The difference between this and TIMEOUT, is that TIMEOUT happens
830 # when rebooting to the test kernel. This slee 726 # when rebooting to the test kernel. This sleep time happens
831 # after a test has completed and we are about 727 # after a test has completed and we are about to start running
832 # another test. If a reboot to the reliable ke 728 # another test. If a reboot to the reliable kernel happens,
833 # we wait SLEEP_TIME for the console to stop p 729 # we wait SLEEP_TIME for the console to stop producing output
834 # before starting the next test. 730 # before starting the next test.
835 # 731 #
836 # You can speed up reboot times even more by s 732 # You can speed up reboot times even more by setting REBOOT_SUCCESS_LINE.
837 # (default 60) 733 # (default 60)
838 #SLEEP_TIME = 60 734 #SLEEP_TIME = 60
839 735
840 # The time in between bisects to sleep (in sec 736 # The time in between bisects to sleep (in seconds)
841 # (default 60) 737 # (default 60)
842 #BISECT_SLEEP_TIME = 60 738 #BISECT_SLEEP_TIME = 60
843 739
844 # The max wait time (in seconds) for waiting f 740 # The max wait time (in seconds) for waiting for the console to finish.
845 # If for some reason, the console is outputtin 741 # If for some reason, the console is outputting content without
846 # ever finishing, this will cause ktest to get 742 # ever finishing, this will cause ktest to get stuck. This
847 # option is the max time ktest will wait for t 743 # option is the max time ktest will wait for the monitor (console)
848 # to settle down before continuing. 744 # to settle down before continuing.
849 # (default 1800) 745 # (default 1800)
850 #MAX_MONITOR_WAIT 746 #MAX_MONITOR_WAIT
851 747
852 # The time in between patch checks to sleep (i 748 # The time in between patch checks to sleep (in seconds)
853 # (default 60) 749 # (default 60)
854 #PATCHCHECK_SLEEP_TIME = 60 750 #PATCHCHECK_SLEEP_TIME = 60
855 751
856 # Reboot the target box on error (default 0) 752 # Reboot the target box on error (default 0)
857 #REBOOT_ON_ERROR = 0 753 #REBOOT_ON_ERROR = 0
858 754
859 # Power off the target on error (ignored if RE 755 # Power off the target on error (ignored if REBOOT_ON_ERROR is set)
860 # Note, this is a DEFAULT section only option 756 # Note, this is a DEFAULT section only option.
861 # (default 0) 757 # (default 0)
862 #POWEROFF_ON_ERROR = 0 758 #POWEROFF_ON_ERROR = 0
863 759
864 # Power off the target after all tests have co 760 # Power off the target after all tests have completed successfully
865 # Note, this is a DEFAULT section only option 761 # Note, this is a DEFAULT section only option.
866 # (default 0) 762 # (default 0)
867 #POWEROFF_ON_SUCCESS = 0 763 #POWEROFF_ON_SUCCESS = 0
868 764
869 # Reboot the target after all test completed s 765 # Reboot the target after all test completed successfully (default 1)
870 # (ignored if POWEROFF_ON_SUCCESS is set) 766 # (ignored if POWEROFF_ON_SUCCESS is set)
871 #REBOOT_ON_SUCCESS = 1 767 #REBOOT_ON_SUCCESS = 1
872 768
873 # In case there are issues with rebooting, you !! 769 # In case there are isses with rebooting, you can specify this
874 # to always powercycle after this amount of ti 770 # to always powercycle after this amount of time after calling
875 # reboot. 771 # reboot.
876 # Note, POWERCYCLE_AFTER_REBOOT = 0 does NOT d 772 # Note, POWERCYCLE_AFTER_REBOOT = 0 does NOT disable it. It just
877 # makes it powercycle immediately after reboot 773 # makes it powercycle immediately after rebooting. Do not define
878 # it if you do not want it. 774 # it if you do not want it.
879 # (default undefined) 775 # (default undefined)
880 #POWERCYCLE_AFTER_REBOOT = 5 776 #POWERCYCLE_AFTER_REBOOT = 5
881 777
882 # In case there's issues with halting, you can !! 778 # In case there's isses with halting, you can specify this
883 # to always poweroff after this amount of time 779 # to always poweroff after this amount of time after calling
884 # halt. 780 # halt.
885 # Note, POWEROFF_AFTER_HALT = 0 does NOT disab 781 # Note, POWEROFF_AFTER_HALT = 0 does NOT disable it. It just
886 # makes it poweroff immediately after halting. 782 # makes it poweroff immediately after halting. Do not define
887 # it if you do not want it. 783 # it if you do not want it.
888 # (default undefined) 784 # (default undefined)
889 #POWEROFF_AFTER_HALT = 20 785 #POWEROFF_AFTER_HALT = 20
890 786
891 # A script or command to power off the box (de 787 # A script or command to power off the box (default undefined)
892 # Needed for POWEROFF_ON_ERROR and SUCCESS 788 # Needed for POWEROFF_ON_ERROR and SUCCESS
893 # 789 #
894 # Example for digital loggers power switch: 790 # Example for digital loggers power switch:
895 #POWER_OFF = wget --no-proxy -O /dev/null -q 791 #POWER_OFF = wget --no-proxy -O /dev/null -q --auth-no-challenge 'http://admin:admin@power/outlet?5=OFF'
896 # 792 #
897 # Example for a virtual guest call "Guest". 793 # Example for a virtual guest call "Guest".
898 #POWER_OFF = virsh destroy Guest 794 #POWER_OFF = virsh destroy Guest
899 795
900 # To have the build fail on "new" warnings, cr 796 # To have the build fail on "new" warnings, create a file that
901 # contains a list of all known warnings (they 797 # contains a list of all known warnings (they must match exactly
902 # to the line with 'warning:', 'error:' or 'Er 798 # to the line with 'warning:', 'error:' or 'Error:'. If the option
903 # WARNINGS_FILE is set, then that file will be 799 # WARNINGS_FILE is set, then that file will be read, and if the
904 # build detects a warning, it will examine thi 800 # build detects a warning, it will examine this file and if the
905 # warning does not exist in it, it will fail t 801 # warning does not exist in it, it will fail the build.
906 # 802 #
907 # Note, if this option is defined to a file th 803 # Note, if this option is defined to a file that does not exist
908 # then any warning will fail the build. 804 # then any warning will fail the build.
909 # (see make_warnings_file below) 805 # (see make_warnings_file below)
910 # 806 #
911 # (optional, default undefined) 807 # (optional, default undefined)
912 #WARNINGS_FILE = ${OUTPUT_DIR}/warnings_file 808 #WARNINGS_FILE = ${OUTPUT_DIR}/warnings_file
913 809
914 # The way to execute a command on the target 810 # The way to execute a command on the target
915 # (default ssh $SSH_USER@$MACHINE $SSH_COMMAND 811 # (default ssh $SSH_USER@$MACHINE $SSH_COMMAND";)
916 # The variables SSH_USER, MACHINE and SSH_COMM 812 # The variables SSH_USER, MACHINE and SSH_COMMAND are defined
917 #SSH_EXEC = ssh $SSH_USER@$MACHINE $SSH_COMMAN 813 #SSH_EXEC = ssh $SSH_USER@$MACHINE $SSH_COMMAND";
918 814
919 # The way to copy a file to the target (instal 815 # The way to copy a file to the target (install and modules)
920 # (default scp $SRC_FILE $SSH_USER@$MACHINE:$D 816 # (default scp $SRC_FILE $SSH_USER@$MACHINE:$DST_FILE)
921 # The variables SSH_USER, MACHINE are defined 817 # The variables SSH_USER, MACHINE are defined by the config
922 # SRC_FILE and DST_FILE are ktest internal var 818 # SRC_FILE and DST_FILE are ktest internal variables and
923 # should only have '$' and not the '${}' notat 819 # should only have '$' and not the '${}' notation.
924 # (default scp $SRC_FILE ${SSH_USER}@${MACHINE 820 # (default scp $SRC_FILE ${SSH_USER}@${MACHINE}:$DST_FILE)
925 #SCP_TO_TARGET = echo skip scp for $SRC_FILE $ 821 #SCP_TO_TARGET = echo skip scp for $SRC_FILE $DST_FILE
926 822
927 # If install needs to be different than module 823 # If install needs to be different than modules, then this
928 # option will override the SCP_TO_TARGET for i 824 # option will override the SCP_TO_TARGET for installation.
929 # (default ${SCP_TO_TARGET} ) 825 # (default ${SCP_TO_TARGET} )
930 #SCP_TO_TARGET_INSTALL = scp $SRC_FILE tftp@tf 826 #SCP_TO_TARGET_INSTALL = scp $SRC_FILE tftp@tftpserver:$DST_FILE
931 827
932 # The nice way to reboot the target 828 # The nice way to reboot the target
933 # (default ssh $SSH_USER@$MACHINE reboot) 829 # (default ssh $SSH_USER@$MACHINE reboot)
934 # The variables SSH_USER and MACHINE are defin 830 # The variables SSH_USER and MACHINE are defined.
935 #REBOOT = ssh $SSH_USER@$MACHINE reboot 831 #REBOOT = ssh $SSH_USER@$MACHINE reboot
936 832
937 # The return code of REBOOT <<
938 # (default 255) <<
939 #REBOOT_RETURN_CODE = 255 <<
940 <<
941 # The way triple faults are detected is by tes 833 # The way triple faults are detected is by testing the kernel
942 # banner. If the kernel banner for the kernel 834 # banner. If the kernel banner for the kernel we are testing is
943 # found, and then later a kernel banner for an 835 # found, and then later a kernel banner for another kernel version
944 # is found, it is considered that we encounter 836 # is found, it is considered that we encountered a triple fault,
945 # and there is no panic or callback, but simpl 837 # and there is no panic or callback, but simply a reboot.
946 # To disable this (because it did a false posi 838 # To disable this (because it did a false positive) set the following
947 # to 0. 839 # to 0.
948 # (default 1) 840 # (default 1)
949 #DETECT_TRIPLE_FAULT = 0 841 #DETECT_TRIPLE_FAULT = 0
950 842
951 # All options in the config file should be eit 843 # All options in the config file should be either used by ktest
952 # or could be used within a value of another o 844 # or could be used within a value of another option. If an option
953 # in the config file is not used, ktest will w 845 # in the config file is not used, ktest will warn about it and ask
954 # if you want to continue. 846 # if you want to continue.
955 # 847 #
956 # If you don't care if there are non-used opti 848 # If you don't care if there are non-used options, enable this
957 # option. Be careful though, a non-used option 849 # option. Be careful though, a non-used option is usually a sign
958 # of an option name being typed incorrectly. 850 # of an option name being typed incorrectly.
959 # (default 0) 851 # (default 0)
960 #IGNORE_UNUSED = 1 852 #IGNORE_UNUSED = 1
961 853
962 # When testing a kernel that happens to have W 854 # When testing a kernel that happens to have WARNINGs, and call
963 # traces, ktest.pl will detect these and fail 855 # traces, ktest.pl will detect these and fail a boot or test run
964 # due to warnings. By setting this option, kte 856 # due to warnings. By setting this option, ktest will ignore
965 # call traces, and will not fail a test if the 857 # call traces, and will not fail a test if the kernel produces
966 # an oops. Use this option with care. 858 # an oops. Use this option with care.
967 # (default 0) 859 # (default 0)
968 #IGNORE_ERRORS = 1 860 #IGNORE_ERRORS = 1
969 861
970 #### Per test run options #### 862 #### Per test run options ####
971 # The following options are only allowed in TE 863 # The following options are only allowed in TEST_START sections.
972 # They are ignored in the DEFAULTS sections. 864 # They are ignored in the DEFAULTS sections.
973 # 865 #
974 # All of these are optional and undefined by d 866 # All of these are optional and undefined by default, although
975 # some of these options are required for TEST 867 # some of these options are required for TEST_TYPE of patchcheck
976 # and bisect. 868 # and bisect.
977 # 869 #
978 # 870 #
979 # CHECKOUT = branch 871 # CHECKOUT = branch
980 # 872 #
981 # If the BUILD_DIR is a git repository, then 873 # If the BUILD_DIR is a git repository, then you can set this option
982 # to checkout the given branch before running 874 # to checkout the given branch before running the TEST. If you
983 # specify this for the first run, that branch 875 # specify this for the first run, that branch will be used for
984 # all preceding tests until a new CHECKOUT is 876 # all preceding tests until a new CHECKOUT is set.
985 # 877 #
986 # 878 #
987 # TEST_NAME = name 879 # TEST_NAME = name
988 # 880 #
989 # If you want the test to have a name that is 881 # If you want the test to have a name that is displayed in
990 # the test result banner at the end of the te 882 # the test result banner at the end of the test, then use this
991 # option. This is useful to search for the RE 883 # option. This is useful to search for the RESULT keyword and
992 # not have to translate a test number to a te 884 # not have to translate a test number to a test in the config.
993 # 885 #
994 # For TEST_TYPE = patchcheck 886 # For TEST_TYPE = patchcheck
995 # 887 #
996 # This expects the BUILD_DIR to be a git repo 888 # This expects the BUILD_DIR to be a git repository, and
997 # will checkout the PATCHCHECK_START commit. 889 # will checkout the PATCHCHECK_START commit.
998 # 890 #
999 # The option BUILD_TYPE will be ignored. 891 # The option BUILD_TYPE will be ignored.
1000 # 892 #
1001 # The MIN_CONFIG will be used for all builds 893 # The MIN_CONFIG will be used for all builds of the patchcheck. The build type
1002 # used for patchcheck is oldconfig. 894 # used for patchcheck is oldconfig.
1003 # 895 #
1004 # PATCHCHECK_START is required and is the fi 896 # PATCHCHECK_START is required and is the first patch to
1005 # test (the SHA1 of the commit). You may al 897 # test (the SHA1 of the commit). You may also specify anything
1006 # that git checkout allows (branch name, ta !! 898 # that git checkout allows (branch name, tage, HEAD~3).
1007 # 899 #
1008 # PATCHCHECK_END is the last patch to check 900 # PATCHCHECK_END is the last patch to check (default HEAD)
1009 # 901 #
1010 # PATCHCHECK_CHERRY if set to non zero, then <<
1011 # performed against PATCHCHECK_START and <<
1012 # <<
1013 # git cherry ${PATCHCHECK_START} ${PATCH <<
1014 # <<
1015 # Then the changes found will be tested. <<
1016 # <<
1017 # Note, PATCHCHECK_CHERRY requires PATCH <<
1018 # (default 0) <<
1019 # <<
1020 # PATCHCHECK_TYPE is required and is the typ 902 # PATCHCHECK_TYPE is required and is the type of test to run:
1021 # build, boot, test. 903 # build, boot, test.
1022 # 904 #
1023 # Note, the build test will look for warnin 905 # Note, the build test will look for warnings, if a warning occurred
1024 # in a file that a commit touches, the bu 906 # in a file that a commit touches, the build will fail, unless
1025 # IGNORE_WARNINGS is set for the given co 907 # IGNORE_WARNINGS is set for the given commit's sha1
1026 # 908 #
1027 # IGNORE_WARNINGS can be used to disable th 909 # IGNORE_WARNINGS can be used to disable the failure of patchcheck
1028 # on a particular commit (SHA1). You can !! 910 # on a particuler commit (SHA1). You can add more than one commit
1029 # by adding a list of SHA1s that are spac 911 # by adding a list of SHA1s that are space delimited.
1030 # 912 #
1031 # If BUILD_NOCLEAN is set, then make mrprop 913 # If BUILD_NOCLEAN is set, then make mrproper will not be run on
1032 # any of the builds, just like all other TE 914 # any of the builds, just like all other TEST_TYPE tests. But
1033 # what makes patchcheck different from the 915 # what makes patchcheck different from the other tests, is if
1034 # BUILD_NOCLEAN is not set, only the first 916 # BUILD_NOCLEAN is not set, only the first and last patch run
1035 # make mrproper. This helps speed up the te 917 # make mrproper. This helps speed up the test.
1036 # 918 #
1037 # Example: 919 # Example:
1038 # TEST_START 920 # TEST_START
1039 # TEST_TYPE = patchcheck 921 # TEST_TYPE = patchcheck
1040 # CHECKOUT = mybranch 922 # CHECKOUT = mybranch
1041 # PATCHCHECK_TYPE = boot 923 # PATCHCHECK_TYPE = boot
1042 # PATCHCHECK_START = 747e94ae3d1b4c9bf5380e 924 # PATCHCHECK_START = 747e94ae3d1b4c9bf5380e569f614eb9040b79e7
1043 # PATCHCHECK_END = HEAD~2 925 # PATCHCHECK_END = HEAD~2
1044 # IGNORE_WARNINGS = 42f9c6b69b54946ffc0515f 926 # IGNORE_WARNINGS = 42f9c6b69b54946ffc0515f57d01dc7f5c0e4712 0c17ca2c7187f431d8ffc79e81addc730f33d128
1045 # 927 #
1046 # 928 #
1047 # 929 #
1048 # For TEST_TYPE = bisect 930 # For TEST_TYPE = bisect
1049 # 931 #
1050 # You can specify a git bisect if the BUILD_ 932 # You can specify a git bisect if the BUILD_DIR is a git repository.
1051 # The MIN_CONFIG will be used for all builds 933 # The MIN_CONFIG will be used for all builds of the bisect. The build type
1052 # used for bisecting is oldconfig. 934 # used for bisecting is oldconfig.
1053 # 935 #
1054 # The option BUILD_TYPE will be ignored. 936 # The option BUILD_TYPE will be ignored.
1055 # 937 #
1056 # BISECT_TYPE is the type of test to perform 938 # BISECT_TYPE is the type of test to perform:
1057 # build - bad fails to build 939 # build - bad fails to build
1058 # boot - bad builds but fails to boo 940 # boot - bad builds but fails to boot
1059 # test - bad boots but fails a test 941 # test - bad boots but fails a test
1060 # 942 #
1061 # BISECT_GOOD is the commit (SHA1) to label a 943 # BISECT_GOOD is the commit (SHA1) to label as good (accepts all git good commit types)
1062 # BISECT_BAD is the commit to label as bad (a 944 # BISECT_BAD is the commit to label as bad (accepts all git bad commit types)
1063 # 945 #
1064 # The above three options are required for a 946 # The above three options are required for a bisect operation.
1065 # 947 #
1066 # BISECT_REPLAY = /path/to/replay/file (optio 948 # BISECT_REPLAY = /path/to/replay/file (optional, default undefined)
1067 # 949 #
1068 # If an operation failed in the bisect that 950 # If an operation failed in the bisect that was not expected to
1069 # fail. Then the test ends. The state of th 951 # fail. Then the test ends. The state of the BUILD_DIR will be
1070 # left off at where the failure occurred. Y 952 # left off at where the failure occurred. You can examine the
1071 # reason for the failure, and perhaps even 953 # reason for the failure, and perhaps even find a git commit
1072 # that would work to continue with. You can 954 # that would work to continue with. You can run:
1073 # 955 #
1074 # git bisect log > /path/to/replay/file 956 # git bisect log > /path/to/replay/file
1075 # 957 #
1076 # The adding: 958 # The adding:
1077 # 959 #
1078 # BISECT_REPLAY= /path/to/replay/file 960 # BISECT_REPLAY= /path/to/replay/file
1079 # 961 #
1080 # And running the test again. The test will 962 # And running the test again. The test will perform the initial
1081 # git bisect start, git bisect good, and g 963 # git bisect start, git bisect good, and git bisect bad, and
1082 # then it will run git bisect replay on th 964 # then it will run git bisect replay on this file, before
1083 # continuing with the bisect. 965 # continuing with the bisect.
1084 # 966 #
1085 # BISECT_START = commit (optional, default un 967 # BISECT_START = commit (optional, default undefined)
1086 # 968 #
1087 # As with BISECT_REPLAY, if the test failed 969 # As with BISECT_REPLAY, if the test failed on a commit that
1088 # just happen to have a bad commit in the m 970 # just happen to have a bad commit in the middle of the bisect,
1089 # and you need to skip it. If BISECT_START 971 # and you need to skip it. If BISECT_START is defined, it
1090 # will checkout that commit after doing the 972 # will checkout that commit after doing the initial git bisect start,
1091 # git bisect good, git bisect bad, and runn 973 # git bisect good, git bisect bad, and running the git bisect replay
1092 # if the BISECT_REPLAY is set. 974 # if the BISECT_REPLAY is set.
1093 # 975 #
1094 # BISECT_SKIP = 1 (optional, default 0) 976 # BISECT_SKIP = 1 (optional, default 0)
1095 # 977 #
1096 # If BISECT_TYPE is set to test but the bui 978 # If BISECT_TYPE is set to test but the build fails, ktest will
1097 # simply fail the test and end their. You c 979 # simply fail the test and end their. You could use BISECT_REPLAY
1098 # and BISECT_START to resume after you foun 980 # and BISECT_START to resume after you found a new starting point,
1099 # or you could set BISECT_SKIP to 1. If BIS 981 # or you could set BISECT_SKIP to 1. If BISECT_SKIP is set to 1,
1100 # when something other than the BISECT_TYPE 982 # when something other than the BISECT_TYPE fails, ktest.pl will
1101 # run "git bisect skip" and try again. 983 # run "git bisect skip" and try again.
1102 # 984 #
1103 # BISECT_FILES = <path> (optional, default un 985 # BISECT_FILES = <path> (optional, default undefined)
1104 # 986 #
1105 # To just run the git bisect on a specific 987 # To just run the git bisect on a specific path, set BISECT_FILES.
1106 # For example: 988 # For example:
1107 # 989 #
1108 # BISECT_FILES = arch/x86 kernel/time 990 # BISECT_FILES = arch/x86 kernel/time
1109 # 991 #
1110 # Will run the bisect with "git bisect star 992 # Will run the bisect with "git bisect start -- arch/x86 kernel/time"
1111 # 993 #
1112 # BISECT_REVERSE = 1 (optional, default 0) 994 # BISECT_REVERSE = 1 (optional, default 0)
1113 # 995 #
1114 # In those strange instances where it was b 996 # In those strange instances where it was broken forever
1115 # and you are trying to find where it start 997 # and you are trying to find where it started to work!
1116 # Set BISECT_GOOD to the commit that was la 998 # Set BISECT_GOOD to the commit that was last known to fail
1117 # Set BISECT_BAD to the commit that is know 999 # Set BISECT_BAD to the commit that is known to start working.
1118 # With BISECT_REVERSE = 1, The test will co 1000 # With BISECT_REVERSE = 1, The test will consider failures as
1119 # good, and success as bad. 1001 # good, and success as bad.
1120 # 1002 #
1121 # BISECT_MANUAL = 1 (optional, default 0) 1003 # BISECT_MANUAL = 1 (optional, default 0)
1122 # 1004 #
1123 # In case there's a problem with automating 1005 # In case there's a problem with automating the bisect for
1124 # whatever reason. (Can't reboot, want to i 1006 # whatever reason. (Can't reboot, want to inspect each iteration)
1125 # Doing a BISECT_MANUAL will have the test 1007 # Doing a BISECT_MANUAL will have the test wait for you to
1126 # tell it if the test passed or failed afte 1008 # tell it if the test passed or failed after each iteration.
1127 # This is basically the same as running git !! 1009 # This is basicall the same as running git bisect yourself
1128 # but ktest will rebuild and install the ke 1010 # but ktest will rebuild and install the kernel for you.
1129 # 1011 #
1130 # BISECT_CHECK = 1 (optional, default 0) 1012 # BISECT_CHECK = 1 (optional, default 0)
1131 # 1013 #
1132 # Just to be sure the good is good and bad 1014 # Just to be sure the good is good and bad is bad, setting
1133 # BISECT_CHECK to 1 will start the bisect b 1015 # BISECT_CHECK to 1 will start the bisect by first checking
1134 # out BISECT_BAD and makes sure it fails, t 1016 # out BISECT_BAD and makes sure it fails, then it will check
1135 # out BISECT_GOOD and makes sure it succeed 1017 # out BISECT_GOOD and makes sure it succeeds before starting
1136 # the bisect (it works for BISECT_REVERSE t 1018 # the bisect (it works for BISECT_REVERSE too).
1137 # 1019 #
1138 # You can limit the test to just check BISE 1020 # You can limit the test to just check BISECT_GOOD or
1139 # BISECT_BAD with BISECT_CHECK = good or 1021 # BISECT_BAD with BISECT_CHECK = good or
1140 # BISECT_CHECK = bad, respectively. 1022 # BISECT_CHECK = bad, respectively.
1141 # 1023 #
1142 # BISECT_TRIES = 5 (optional, default 1) <<
1143 # <<
1144 # For those cases that it takes several tri <<
1145 # the BISECT_TRIES is useful. It is the num <<
1146 # test is ran before it says the kernel is <<
1147 # will stop trying and mark the current SHA <<
1148 # <<
1149 # Note, as with all race bugs, there's no g <<
1150 # it succeeds, it is really a good bisect. <<
1151 # the bug is some what reliable. <<
1152 # <<
1153 # You can set BISECT_TRIES to zero, and all <<
1154 # good, unless you also set BISECT_MANUAL. <<
1155 # <<
1156 # BISECT_RET_GOOD = 0 (optional, default unde 1024 # BISECT_RET_GOOD = 0 (optional, default undefined)
1157 # 1025 #
1158 # In case the specificed test returns somet 1026 # In case the specificed test returns something other than just
1159 # 0 for good, and non-zero for bad, you can 1027 # 0 for good, and non-zero for bad, you can override 0 being
1160 # good by defining BISECT_RET_GOOD. 1028 # good by defining BISECT_RET_GOOD.
1161 # 1029 #
1162 # BISECT_RET_BAD = 1 (optional, default undef 1030 # BISECT_RET_BAD = 1 (optional, default undefined)
1163 # 1031 #
1164 # In case the specificed test returns somet 1032 # In case the specificed test returns something other than just
1165 # 0 for good, and non-zero for bad, you can 1033 # 0 for good, and non-zero for bad, you can override non-zero being
1166 # bad by defining BISECT_RET_BAD. 1034 # bad by defining BISECT_RET_BAD.
1167 # 1035 #
1168 # BISECT_RET_ABORT = 255 (optional, default u 1036 # BISECT_RET_ABORT = 255 (optional, default undefined)
1169 # 1037 #
1170 # If you need to abort the bisect if the te 1038 # If you need to abort the bisect if the test discovers something
1171 # that was wrong, you can define BISECT_RET 1039 # that was wrong, you can define BISECT_RET_ABORT to be the error
1172 # code returned by the test in order to abo 1040 # code returned by the test in order to abort the bisect.
1173 # 1041 #
1174 # BISECT_RET_SKIP = 2 (optional, default unde 1042 # BISECT_RET_SKIP = 2 (optional, default undefined)
1175 # 1043 #
1176 # If the test detects that the current comm 1044 # If the test detects that the current commit is neither good
1177 # nor bad, but something else happened (ano 1045 # nor bad, but something else happened (another bug detected)
1178 # you can specify BISECT_RET_SKIP to an err 1046 # you can specify BISECT_RET_SKIP to an error code that the
1179 # test returns when it should skip the curr 1047 # test returns when it should skip the current commit.
1180 # 1048 #
1181 # BISECT_RET_DEFAULT = good (optional, defaul 1049 # BISECT_RET_DEFAULT = good (optional, default undefined)
1182 # 1050 #
1183 # You can override the default of what to d 1051 # You can override the default of what to do when the above
1184 # options are not hit. This may be one of, 1052 # options are not hit. This may be one of, "good", "bad",
1185 # "abort" or "skip" (without the quotes). 1053 # "abort" or "skip" (without the quotes).
1186 # 1054 #
1187 # Note, if you do not define any of the pre 1055 # Note, if you do not define any of the previous BISECT_RET_*
1188 # and define BISECT_RET_DEFAULT, all bisect 1056 # and define BISECT_RET_DEFAULT, all bisects results will do
1189 # what the BISECT_RET_DEFAULT has. 1057 # what the BISECT_RET_DEFAULT has.
1190 # 1058 #
1191 # 1059 #
1192 # Example: 1060 # Example:
1193 # TEST_START 1061 # TEST_START
1194 # TEST_TYPE = bisect 1062 # TEST_TYPE = bisect
1195 # BISECT_GOOD = v2.6.36 1063 # BISECT_GOOD = v2.6.36
1196 # BISECT_BAD = b5153163ed580e00c67bdfecb02b 1064 # BISECT_BAD = b5153163ed580e00c67bdfecb02b2e3843817b3e
1197 # BISECT_TYPE = build 1065 # BISECT_TYPE = build
1198 # MIN_CONFIG = /home/test/config-bisect 1066 # MIN_CONFIG = /home/test/config-bisect
1199 # 1067 #
1200 # 1068 #
1201 # 1069 #
1202 # For TEST_TYPE = config_bisect 1070 # For TEST_TYPE = config_bisect
1203 # 1071 #
1204 # In those cases that you have two different 1072 # In those cases that you have two different configs. One of them
1205 # work, the other does not, and you do not k 1073 # work, the other does not, and you do not know what config causes
1206 # the problem. 1074 # the problem.
1207 # The TEST_TYPE config_bisect will bisect th 1075 # The TEST_TYPE config_bisect will bisect the bad config looking for
1208 # what config causes the failure. 1076 # what config causes the failure.
1209 # 1077 #
1210 # The way it works is this: 1078 # The way it works is this:
1211 # 1079 #
1212 # You can specify a good config with CONFIG !! 1080 # First it finds a config to work with. Since a different version, or
1213 # will use the MIN_CONFIG, and if that's no !! 1081 # MIN_CONFIG may cause different dependecies, it must run through this
1214 # the config that comes with "make defconfi !! 1082 # preparation.
1215 # !! 1083 #
1216 # It runs both the good and bad configs thr !! 1084 # Overwrites any config set in the bad config with a config set in
1217 # make sure that they are set up for the ke !! 1085 # either the MIN_CONFIG or ADD_CONFIG. Thus, make sure these configs
1218 # !! 1086 # are minimal and do not disable configs you want to test:
1219 # It then reads the configs that are set, a !! 1087 # (ie. # CONFIG_FOO is not set).
1220 # not set for both the good and bad configs !! 1088 #
1221 # It will set half of the good configs with !! 1089 # An oldconfig is run on the bad config and any new config that
1222 # "set" means to make the bad config match !! 1090 # appears will be added to the configs to test.
1223 # in the good config that is off, will be t !! 1091 #
1224 # config. That is considered a "set"). !! 1092 # Finally, it generates a config with the above result and runs it
1225 # !! 1093 # again through make oldconfig to produce a config that should be
1226 # It tests this new config and if it works, !! 1094 # satisfied by kconfig.
1227 # config, otherwise it becomes the new bad !! 1095 #
1228 # process until there's only one config lef !! 1096 # Then it starts the bisect.
1229 # config. !! 1097 #
1230 # !! 1098 # The configs to test are cut in half. If all the configs in this
1231 # The "bad config" can also be a config tha !! 1099 # half depend on a config in the other half, then the other half
1232 # disabled because it depended on something !! 1100 # is tested instead. If no configs are enabled by either half, then
1233 # !! 1101 # this means a circular dependency exists and the test fails.
1234 # During this process, it saves the current !! 1102 #
1235 # ${TMP_DIR}/good_config and ${TMP_DIR}/bad !! 1103 # A config is created with the test half, and the bisect test is run.
1236 # If you stop the test, you can copy them t !! 1104 #
1237 # reuse them again. !! 1105 # If the bisect succeeds, then all configs in the generated config
1238 # !! 1106 # are removed from the configs to test and added to the configs that
1239 # Although the MIN_CONFIG may be the config !! 1107 # will be enabled for all builds (they will be enabled, but not be part
1240 # MIN_CONFIG is ignored. !! 1108 # of the configs to examine).
>> 1109 #
>> 1110 # If the bisect fails, then all test configs that were not enabled by
>> 1111 # the config file are removed from the test. These configs will not
>> 1112 # be enabled in future tests. Since current config failed, we consider
>> 1113 # this to be a subset of the config that we started with.
>> 1114 #
>> 1115 # When we are down to one config, it is considered the bad config.
>> 1116 #
>> 1117 # Note, the config chosen may not be the true bad config. Due to
>> 1118 # dependencies and selections of the kbuild system, mulitple
>> 1119 # configs may be needed to cause a failure. If you disable the
>> 1120 # config that was found and restart the test, if the test fails
>> 1121 # again, it is recommended to rerun the config_bisect with a new
>> 1122 # bad config without the found config enabled.
1241 # 1123 #
1242 # The option BUILD_TYPE will be ignored. 1124 # The option BUILD_TYPE will be ignored.
1243 # 1125 #
1244 # CONFIG_BISECT_TYPE is the type of test to 1126 # CONFIG_BISECT_TYPE is the type of test to perform:
1245 # build - bad fails to build 1127 # build - bad fails to build
1246 # boot - bad builds but fails to boo 1128 # boot - bad builds but fails to boot
1247 # test - bad boots but fails a test 1129 # test - bad boots but fails a test
1248 # 1130 #
1249 # CONFIG_BISECT is the config that failed to 1131 # CONFIG_BISECT is the config that failed to boot
1250 # 1132 #
1251 # If BISECT_MANUAL is set, it will pause bet 1133 # If BISECT_MANUAL is set, it will pause between iterations.
1252 # This is useful to use just ktest.pl just f 1134 # This is useful to use just ktest.pl just for the config bisect.
1253 # If you set it to build, it will run the bi 1135 # If you set it to build, it will run the bisect and you can
1254 # control what happens in between iterations 1136 # control what happens in between iterations. It will ask you if
1255 # the test succeeded or not and continue the 1137 # the test succeeded or not and continue the config bisect.
1256 # 1138 #
1257 # CONFIG_BISECT_GOOD (optional) 1139 # CONFIG_BISECT_GOOD (optional)
1258 # If you have a good config to start with, t 1140 # If you have a good config to start with, then you
1259 # can specify it with CONFIG_BISECT_GOOD. Ot 1141 # can specify it with CONFIG_BISECT_GOOD. Otherwise
1260 # the MIN_CONFIG is the base, if MIN_CONFIG !! 1142 # the MIN_CONFIG is the base.
1261 # It will build a config with "make defconfi <<
1262 # 1143 #
1263 # CONFIG_BISECT_CHECK (optional) 1144 # CONFIG_BISECT_CHECK (optional)
1264 # Set this to 1 if you want to confirm that 1145 # Set this to 1 if you want to confirm that the config ktest
1265 # generates (the bad config with the min con 1146 # generates (the bad config with the min config) is still bad.
1266 # It may be that the min config fixes what b 1147 # It may be that the min config fixes what broke the bad config
1267 # and the test will not return a result. 1148 # and the test will not return a result.
1268 # Set it to "good" to test only the good con <<
1269 # to "bad" to only test the bad config. <<
1270 # <<
1271 # CONFIG_BISECT_EXEC (optional) <<
1272 # The config bisect is a separate program th <<
1273 # By default, it will look for: <<
1274 # `pwd`/config-bisect.pl # the location kt <<
1275 # If it does not find it there, it will look <<
1276 # `dirname <ktest.pl>`/config-bisect.pl # <<
1277 # If it does not find it there, it will look <<
1278 # ${BUILD_DIR}/tools/testing/ktest/config- <<
1279 # Setting CONFIG_BISECT_EXEC will override w <<
1280 # 1149 #
1281 # Example: 1150 # Example:
1282 # TEST_START 1151 # TEST_START
1283 # TEST_TYPE = config_bisect 1152 # TEST_TYPE = config_bisect
1284 # CONFIG_BISECT_TYPE = build 1153 # CONFIG_BISECT_TYPE = build
1285 # CONFIG_BISECT = /home/test/config-bad 1154 # CONFIG_BISECT = /home/test/config-bad
1286 # MIN_CONFIG = /home/test/config-min 1155 # MIN_CONFIG = /home/test/config-min
1287 # BISECT_MANUAL = 1 1156 # BISECT_MANUAL = 1
1288 # 1157 #
1289 # 1158 #
1290 # 1159 #
1291 # For TEST_TYPE = make_min_config 1160 # For TEST_TYPE = make_min_config
1292 # 1161 #
1293 # After doing a make localyesconfig, your ke 1162 # After doing a make localyesconfig, your kernel configuration may
1294 # not be the most useful minimum configurati 1163 # not be the most useful minimum configuration. Having a true minimum
1295 # config that you can use against other conf 1164 # config that you can use against other configs is very useful if
1296 # someone else has a config that breaks on y 1165 # someone else has a config that breaks on your code. By only forcing
1297 # those configurations that are truly requir 1166 # those configurations that are truly required to boot your machine
1298 # will give you less of a chance that one of 1167 # will give you less of a chance that one of your set configurations
1299 # will make the bug go away. This will give 1168 # will make the bug go away. This will give you a better chance to
1300 # be able to reproduce the reported bug matc 1169 # be able to reproduce the reported bug matching the broken config.
1301 # 1170 #
1302 # Note, this does take some time, and may re 1171 # Note, this does take some time, and may require you to run the
1303 # test over night, or perhaps over the weeke 1172 # test over night, or perhaps over the weekend. But it also allows
1304 # you to interrupt it, and gives you the cur 1173 # you to interrupt it, and gives you the current minimum config
1305 # that was found till that time. 1174 # that was found till that time.
1306 # 1175 #
1307 # Note, this test automatically assumes a BU 1176 # Note, this test automatically assumes a BUILD_TYPE of oldconfig
1308 # and its test type acts like boot. 1177 # and its test type acts like boot.
1309 # TODO: add a test version that makes the co 1178 # TODO: add a test version that makes the config do more than just
1310 # boot, like having network access. 1179 # boot, like having network access.
1311 # 1180 #
1312 # To save time, the test does not just grab 1181 # To save time, the test does not just grab any option and test
1313 # it. The Kconfig files are examined to dete 1182 # it. The Kconfig files are examined to determine the dependencies
1314 # of the configs. If a config is chosen that 1183 # of the configs. If a config is chosen that depends on another
1315 # config, that config will be checked first. 1184 # config, that config will be checked first. By checking the
1316 # parents first, we can eliminate whole grou 1185 # parents first, we can eliminate whole groups of configs that
1317 # may have been enabled. 1186 # may have been enabled.
1318 # 1187 #
1319 # For example, if a USB device config is cho 1188 # For example, if a USB device config is chosen and depends on CONFIG_USB,
1320 # the CONFIG_USB will be tested before the d 1189 # the CONFIG_USB will be tested before the device. If CONFIG_USB is
1321 # found not to be needed, it, as well as all 1190 # found not to be needed, it, as well as all configs that depend on
1322 # it, will be disabled and removed from the 1191 # it, will be disabled and removed from the current min_config.
1323 # 1192 #
1324 # OUTPUT_MIN_CONFIG is the path and filename 1193 # OUTPUT_MIN_CONFIG is the path and filename of the file that will
1325 # be created from the MIN_CONFIG. If you in 1194 # be created from the MIN_CONFIG. If you interrupt the test, set
1326 # this file as your new min config, and use 1195 # this file as your new min config, and use it to continue the test.
1327 # This file does not need to exist on start 1196 # This file does not need to exist on start of test.
1328 # This file is not created until a config i 1197 # This file is not created until a config is found that can be removed.
1329 # If this file exists, you will be prompted 1198 # If this file exists, you will be prompted if you want to use it
1330 # as the min_config (overriding MIN_CONFIG) 1199 # as the min_config (overriding MIN_CONFIG) if START_MIN_CONFIG
1331 # is not defined. 1200 # is not defined.
1332 # (required field) 1201 # (required field)
1333 # 1202 #
1334 # START_MIN_CONFIG is the config to use to s 1203 # START_MIN_CONFIG is the config to use to start the test with.
1335 # you can set this as the same OUTPUT_MIN_C 1204 # you can set this as the same OUTPUT_MIN_CONFIG, but if you do
1336 # the OUTPUT_MIN_CONFIG file must exist. 1205 # the OUTPUT_MIN_CONFIG file must exist.
1337 # (default MIN_CONFIG) 1206 # (default MIN_CONFIG)
1338 # 1207 #
1339 # IGNORE_CONFIG is used to specify a config 1208 # IGNORE_CONFIG is used to specify a config file that has configs that
1340 # you already know must be set. Configs are 1209 # you already know must be set. Configs are written here that have
1341 # been tested and proved to be required. It 1210 # been tested and proved to be required. It is best to define this
1342 # file if you intend on interrupting the te 1211 # file if you intend on interrupting the test and running it where
1343 # it left off. New configs that it finds wi 1212 # it left off. New configs that it finds will be written to this file
1344 # and will not be tested again in later run 1213 # and will not be tested again in later runs.
1345 # (optional) 1214 # (optional)
1346 # 1215 #
1347 # MIN_CONFIG_TYPE can be either 'boot' or 't 1216 # MIN_CONFIG_TYPE can be either 'boot' or 'test'. With 'boot' it will
1348 # test if the created config can just boot 1217 # test if the created config can just boot the machine. If this is
1349 # set to 'test', then the TEST option must 1218 # set to 'test', then the TEST option must be defined and the created
1350 # config will not only boot the target, but 1219 # config will not only boot the target, but also make sure that the
1351 # config lets the test succeed. This is use 1220 # config lets the test succeed. This is useful to make sure the final
1352 # config that is generated allows network a 1221 # config that is generated allows network activity (ssh).
1353 # (optional) 1222 # (optional)
1354 # 1223 #
1355 # USE_OUTPUT_MIN_CONFIG set this to 1 if you 1224 # USE_OUTPUT_MIN_CONFIG set this to 1 if you do not want to be prompted
1356 # about using the OUTPUT_MIN_CONFIG as the 1225 # about using the OUTPUT_MIN_CONFIG as the MIN_CONFIG as the starting
1357 # point. Set it to 0 if you want to always 1226 # point. Set it to 0 if you want to always just use the given MIN_CONFIG.
1358 # If it is not defined, it will prompt you 1227 # If it is not defined, it will prompt you to pick which config
1359 # to start with (MIN_CONFIG or OUTPUT_MIN_C 1228 # to start with (MIN_CONFIG or OUTPUT_MIN_CONFIG).
1360 # 1229 #
1361 # Example: 1230 # Example:
1362 # 1231 #
1363 # TEST_TYPE = make_min_config 1232 # TEST_TYPE = make_min_config
1364 # OUTPUT_MIN_CONFIG = /path/to/config-new-mi 1233 # OUTPUT_MIN_CONFIG = /path/to/config-new-min
1365 # START_MIN_CONFIG = /path/to/config-min 1234 # START_MIN_CONFIG = /path/to/config-min
1366 # IGNORE_CONFIG = /path/to/config-tested 1235 # IGNORE_CONFIG = /path/to/config-tested
1367 # MIN_CONFIG_TYPE = test 1236 # MIN_CONFIG_TYPE = test
1368 # TEST = ssh ${USER}@${MACHINE} echo hi 1237 # TEST = ssh ${USER}@${MACHINE} echo hi
1369 # 1238 #
1370 # 1239 #
1371 # 1240 #
1372 # 1241 #
1373 # For TEST_TYPE = make_warnings_file 1242 # For TEST_TYPE = make_warnings_file
1374 # 1243 #
1375 # If you want the build to fail when a new wa 1244 # If you want the build to fail when a new warning is discovered
1376 # you set the WARNINGS_FILE to point to a fil 1245 # you set the WARNINGS_FILE to point to a file of known warnings.
1377 # 1246 #
1378 # The test "make_warnings_file" will let you 1247 # The test "make_warnings_file" will let you create a new warnings
1379 # file before you run other tests, like patch 1248 # file before you run other tests, like patchcheck.
1380 # 1249 #
1381 # What this test does is to run just a build, 1250 # What this test does is to run just a build, you still need to
1382 # specify BUILD_TYPE to tell the test what ty 1251 # specify BUILD_TYPE to tell the test what type of config to use.
1383 # A BUILD_TYPE of nobuild will fail this test 1252 # A BUILD_TYPE of nobuild will fail this test.
1384 # 1253 #
1385 # The test will do the build and scan for all 1254 # The test will do the build and scan for all warnings. Any warning
1386 # it discovers will be saved in the WARNINGS_ 1255 # it discovers will be saved in the WARNINGS_FILE (required) option.
1387 # 1256 #
1388 # It is recommended (but not necessary) to ma 1257 # It is recommended (but not necessary) to make sure BUILD_NOCLEAN is
1389 # off, so that a full build is done (make mrp 1258 # off, so that a full build is done (make mrproper is performed).
1390 # That way, all warnings will be captured. 1259 # That way, all warnings will be captured.
1391 # 1260 #
1392 # Example: 1261 # Example:
1393 # 1262 #
1394 # TEST_TYPE = make_warnings_file 1263 # TEST_TYPE = make_warnings_file
1395 # WARNINGS_FILE = ${OUTPUT_DIR} 1264 # WARNINGS_FILE = ${OUTPUT_DIR}
1396 # BUILD_TYPE = useconfig:oldconfig 1265 # BUILD_TYPE = useconfig:oldconfig
1397 # CHECKOUT = v3.8 1266 # CHECKOUT = v3.8
1398 # BUILD_NOCLEAN = 0 1267 # BUILD_NOCLEAN = 0
1399 # 1268 #
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.