You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
echo -e "String1\nString2" | (/Users/Stanislaw/workspace/inbox-active-code/FileCheck.py/tests/integration/tools/FileCheck/FileCheck /Users/Stanislaw/workspace/inbox-active-code/FileCheck.py/tests/integration/tests/examples/check-commands/CHECK-EMPTY/Failure/CHECK-EMPTY.check 2>&1; test $? = 1)
/Users/Stanislaw/workspace/inbox-active-code/FileCheck.py/tests/integration/tools/FileCheck
/Users/Stanislaw/workspace/inbox-active-code/FileCheck.py/tests/integration/tests/examples/check-commands/CHECK-EMPTY/Failure/CHECK-EMPTY.check:2:13: error: CHECK-EMPTY: is not on the line after the previous match
CHECK-EMPTY:
^
<stdin>:3:1: note: 'next' match was here
^
<stdin>:1:8: note: previous match ended here
String1
^
<stdin>:2:1: note: non-matching line after previous match is here
String2
^
What is weird is that according to the output of the LLVM's FileCheck, the line #3 exists in the input, while
echo -e "String1\nString2" | wc -l
2
P.S. If this is resolved somehow, the CHECK-EMPTY.itest-py has to be made just .itest.
The text was updated successfully, but these errors were encountered:
Check file:
Test:
What is weird is that according to the output of the LLVM's FileCheck, the line #3 exists in the input, while
P.S. If this is resolved somehow, the
CHECK-EMPTY.itest-py
has to be made just.itest
.The text was updated successfully, but these errors were encountered: