Lines Matching refs:dump

5 ; so we can check how trace suppression is affected by -dump-input.
18 ; Check -dump-input=<bad value>.
23 ; RUN:               -match-full-lines -dump-input=foobar 2>&1 \
27 ; RUN: %ProtectFileCheckOutput not FileCheck -dump-input=foobar 2>&1 \
30 BADVAL: {{F|f}}ile{{C|c}}heck{{.*}}: for the --dump-input option: Cannot find option named 'foobar'!
33 ; Check -dump-input=help.
38 ; RUN: FileCheck -input-file %t.err -color %t.check -dump-input=help \
42 ; RUN: %ProtectFileCheckOutput FileCheck -dump-input=help \
46 ; Check -dump-input=never.
51 ; FileCheck success, no -v => no dump, no trace.
54 ; RUN:           -match-full-lines -dump-input=never 2>&1 \
58 ; FileCheck fail, no -v => no dump, no trace.
61 ; RUN:               -match-full-lines -dump-input=never 2>&1 \
64 ; FileCheck success, -v => no dump, trace.
67 ; RUN:           -match-full-lines -dump-input=never -v 2>&1 \
70 ; FileCheck fail, -v => no dump, trace.
73 ; RUN:               -match-full-lines -dump-input=never -v 2>&1 \
77 ; Check no -dump-input, which defaults to fail.
80 ; FileCheck success, -v => no dump, no trace.
87 ; FileCheck fail, -v => dump, no trace.
95 ; Check -dump-input=fail.
100 ; FileCheck success, no -v => no dump, no trace.
103 ; RUN:           -match-full-lines -dump-input=fail 2>&1 \
107 ; FileCheck fail, no -v => dump, no trace.
110 ; RUN:               -match-full-lines -dump-input=fail 2>&1 \
113 ; FileCheck success, -v => no dump, no trace.
116 ; RUN:           -match-full-lines -dump-input=fail -v 2>&1 \
120 ; FileCheck fail, -v => dump, no trace.
123 ; RUN:               -match-full-lines -dump-input=fail -v 2>&1 \
128 ; Check -dump-input=always.
131 ; FileCheck success, -v => dump, no trace.
134 ; RUN:           -match-full-lines -dump-input=always -v 2>&1 \
137 ; FileCheck fail, -v => dump, no trace.
140 ; RUN:               -match-full-lines -dump-input=always -v 2>&1 \
145 ; Check multiple -dump-input options.
147 ; This occurs most commonly when a test author specifies -dump-input on a
148 ; specific FileCheck call while a test runner specifies -dump-input in
159 ; fail, fail => fail (FileCheck fail => dump)
162 ; RUN:               -match-full-lines -dump-input=fail -dump-input=fail -v \
174 ; RUN:           -dump-input=help -dump-input=always \
177 ; always, fail => always (FileCheck success => dump)
180 ; RUN:           -match-full-lines -dump-input=always -dump-input=fail \
184 ; fail, never => fail (FileCheck fail => dump)
187 ; RUN:               -match-full-lines -dump-input=fail -dump-input=never -v \
196 ; fail, always => always (FileCheck success => dump)
199 ; RUN:           -match-full-lines -dump-input=fail -dump-input=always \
207 ; always, fail => always (FileCheck success => dump)
208 ; RUN: %ProtectFileCheckOutput FILECHECK_OPTS=-dump-input=always \
210 ; RUN:           -match-full-lines -dump-input=fail -v 2>&1 \
213 ; fail, always => always (FileCheck success => dump)
214 ; RUN: %ProtectFileCheckOutput FILECHECK_OPTS=-dump-input=fail \
216 ; RUN:           -match-full-lines -dump-input=always -v 2>&1 \
226 ; HELP: The following description was requested by -dump-input=help