summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py
diff options
context:
space:
mode:
authorJames Henderson <jh7370@my.bristol.ac.uk>2019-03-12 15:37:34 +0000
committerJames Henderson <jh7370@my.bristol.ac.uk>2019-03-12 15:37:34 +0000
commit662c043628c1dfe9765f3f323cc57931c6d464d4 (patch)
tree60e2094e073b29d3dc66d9d4a55531c8607896ab /lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py
parentc156306bf7b830914167ee2e9f6f78060987acf7 (diff)
downloadbcm5719-llvm-662c043628c1dfe9765f3f323cc57931c6d464d4.tar.gz
bcm5719-llvm-662c043628c1dfe9765f3f323cc57931c6d464d4.zip
[FileCheck]Remove assertions that prevent matching an empty string at file start before CHECK-NEXT/SAME
This patch removes two assertions that were preventing writing of a test that checked an empty line followed by some text. For example: CHECK: {{^$}} CHECK-NEXT: foo() The assertion was because the current location the CHECK-NEXT was scanning from was the start of the buffer. A similar issue occurred with CHECK-SAME. These assertions don't protect against anything, as there is already an error check that checks that CHECK-NEXT/EMPTY/SAME don't appear first in the checks, and the following code works fine if the pointer is at the start of the input. Reviewed by: probinson, thopre, jdenny Differential Revision: https://reviews.llvm.org/D58784 llvm-svn: 355928
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/signals/TestSignalsAPI.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud