maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[lldb] Make TestExprDiagnostics.py pass again after enabling Fix-Its in test 

Commit 83c81c0a46 enabled Fix-Its for top-level
expressions which change the error message of this test here as Clang comes
up with a strange Fix-It for this expression. This patch just changes the
test to declare a void variable so that Clang doesn't see a way to
recover with a Fix-It and change the error message.
This commit is contained in:
Raphael Isemann 2020-03-30 13:48:26 +02:00
parent 821439a45a
commit 502a06fcda
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
lldb/test/API/commands/expression/diagnostics/TestExprDiagnostics.py
View File

@ -60,10 +60,10 @@ class ExprDiagnosticsTestCase(TestBase):
self.assertIn("<user expression 3>:1:10", value.GetError().GetCString())
# Multiline top-level expressions.
value = frame.EvaluateExpression("void x() {}\nvoid foo(unknown_type x) {}", top_level_opts)
value = frame.EvaluateExpression("void x() {}\nvoid foo;", top_level_opts)
self.assertFalse(value.GetError().Success())
self.assertIn("\nvoid foo(unknown_type x) {}\n ^\n", value.GetError().GetCString())
self.assertIn("<user expression 4>:2:10", value.GetError().GetCString())
self.assertIn("\nvoid foo;\n ^", value.GetError().GetCString())
self.assertIn("<user expression 4>:2:6", value.GetError().GetCString())
# Test that we render Clang's 'notes' correctly.
value = frame.EvaluateExpression("struct SFoo{}; struct SFoo { int x; };", top_level_opts)