Lines Matching refs:FileCheck

6 # %ProtectFileCheckOutput should precede a FileCheck call if and only if the
8 # look for redirection or piping of the FileCheck call's stdout or stderr.
12 #   ; Test another program, using FileCheck to verify its textual output.
13 #   ; Only FileCheck's exit status affects test results, so a bare FileCheck
16 #   ; RUN: %t | FileCheck %s
19 #   ; Test FileCheck itself, but only examine its exit status, so a bare
20 #   ; FileCheck call is still sufficient and more convenient for debugging.
22 #   ; RUN: FileCheck -input-file %s %s
26 #   ; Check that the FileCheck trace is off by default.  The first FileCheck
30 #   ; RUN: %ProtectFileCheckOutput FileCheck -input-file %s %s 2>&1 \
31 #   ; RUN: | FileCheck -allow-empty -check-prefix QUIET %s
37 #   ; Check that the FileCheck trace is on when FILECHECK_OPTS=-v.
42 #   ; RUN: FileCheck -dump-input=never -input-file %s %s 2>&1 \
43 #   ; RUN: | FileCheck -check-prefix TRACE %s
50 # developers set FileCheck environment variables (e.g.,
51 # FILECHECK_OPTS=-dump-input=fail) to tweak the output of FileCheck while
52 # debugging tests.  If a developer sets values that affect FileCheck's exit