mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-25 20:23:11 +01:00
dd1fd5b646
Without this patch, `FILECHECK_OPTS` isn't propagated to FileCheck's test suite so that `FILECHECK_OPTS` doesn't inadvertently affect test results by affecting the output of FileCheck calls under test. As a result, `FILECHECK_OPTS` is useless for debugging FileCheck's test suite. In `llvm/test/FileCheck/lit.local.cfg`, this patch provides a new subsitution, `%ProtectFileCheckOutput`, to address this problem for both `FILECHECK_OPTS` and the deprecated `FILECHECK_DUMP_INPUT_ON_FAILURE`. The rest of the patch uses `%ProtectFileCheckOutput` throughout the test suite Fixes PR40284. Reviewed By: probinson, thopre Differential Revision: https://reviews.llvm.org/D65121
23 lines
998 B
Plaintext
23 lines
998 B
Plaintext
; Create a case that produces a simple diagnostic.
|
|
; RUN: echo foo > %t.in
|
|
; CHECK: bar
|
|
|
|
; Run without and with -color. In the former case, FileCheck should suppress
|
|
; color in its diagnostics because stderr is a file.
|
|
; RUN: %ProtectFileCheckOutput not FileCheck %s < %t.in 2> %t.no-color
|
|
; RUN: %ProtectFileCheckOutput not FileCheck -color %s < %t.in 2> %t.color
|
|
|
|
; Check whether color was produced.
|
|
; RUN: FileCheck -check-prefix NO-COLOR %s < %t.no-color
|
|
; RUN: FileCheck -check-prefix COLOR %s < %t.color
|
|
|
|
; Make sure our NO-COLOR and COLOR patterns are sane: they don't match the
|
|
; opposite cases.
|
|
; RUN: not FileCheck -check-prefix COLOR %s < %t.no-color
|
|
; RUN: not FileCheck -check-prefix NO-COLOR %s < %t.color
|
|
|
|
; I don't know of a good way to check for ANSI color codes, so just make sure
|
|
; some new characters show up where those codes should appear.
|
|
; NO-COLOR: : error: CHECK: expected string not found in input
|
|
; COLOR: : {{.+}}error: {{.+}}CHECK: expected string not found in input
|