Lines Matching full:input
2 ; Input file, check file, and directives for checking the size of the context.
4 ; These are designed to be used with -dump-input=fail -vv.
6 ; In the resulting input dump, there are three potential ellipses:
8 ; - S: At the start of the input.
9 ; - M: Between two input lines included by the filter.
10 ; - E: At the end of the input.
12 ; They are all present at -dump-input-context=4. One becomes useless each time
13 ; -dump-input-context is incremented beyond that because then that ellipsis
14 ; becomes equal to or larger than the input lines it elides.
108 ; Now build an alternate set of checks where input lines that might be elided by
162 ; Check -dump-input-context=<bad value>.
166 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
167 ; RUN: -dump-input-context=-1 \
171 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
172 ; RUN: -dump-input-context=foobar \
175 BADVAL: {{F|f}}ile{{C|c}}heck{{.*}}: for the --dump-input-context option: '[[VAL]]' value invalid f…
178 ; Check -dump-input-context explicit values.
183 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
184 ; RUN: -dump-input-context=0 \
189 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
190 ; RUN: -dump-input-context=1 \
195 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
196 ; RUN: -dump-input-context=4 \
201 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
202 ; RUN: -dump-input-context=5 \
207 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
208 ; RUN: -dump-input-context=6 \
213 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
214 ; RUN: -dump-input-context=7 \
217 ; Make sure all is fine when -dump-input-context is far larger than the input.
219 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
220 ; RUN: -dump-input-context=200 \
224 ; Check that -dump-input-context default is 5.
228 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
232 ; Check multiple -dump-input-context options.
234 ; This might occur when a test author specifies -dump-input-context on a
235 ; specific FileCheck call while a test runner specifies -dump-input-context in
246 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
247 ; RUN: -dump-input-context=1 -dump-input-context=1 \
255 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
256 ; RUN: -dump-input-context=0 -dump-input-context=1 \
260 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
261 ; RUN: -dump-input-context=1 -dump-input-context=0 \
268 ; RUN: %ProtectFileCheckOutput FILECHECK_OPTS=-dump-input-context=0 \
269 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
270 ; RUN: -dump-input-context=1 \
273 ; RUN: %ProtectFileCheckOutput FILECHECK_OPTS=-dump-input-context=1 \
274 ; RUN: not FileCheck -dump-input=fail -vv %t.chk < %t.in 2>&1 \
275 ; RUN: -dump-input-context=0 \
279 ; Check how annotations on input lines that might be elided by ellipses affect
283 ; At -dump-input-context=5, the ellipsis is useful but only when annotations on
284 ; elided input lines are considered.
286 ; RUN: not FileCheck -dump-input=fail -vv %t.wide.chk < %t.wide.in 2>&1 \
287 ; RUN: -dump-input-context=5 \
290 ; At -dump-input-context=6, the ellipsis is not useful even when annotations on
291 ; elided input lines are considered.
293 ; RUN: not FileCheck -dump-input=fail -vv %t.wide.chk < %t.wide.in 2>&1 \
294 ; RUN: -dump-input-context=6 \