Remove the @expectedFailure decorator since the bug has been fixed.
rdar://problem/9673664
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@136633 91177308-0d34-0410-b5e6-96231b3b80d8
diff --git a/test/expression_command/radar_9673664/TestExprHelpExamples.py b/test/expression_command/radar_9673664/TestExprHelpExamples.py
index 49d8434..145e6c5 100644
--- a/test/expression_command/radar_9673664/TestExprHelpExamples.py
+++ b/test/expression_command/radar_9673664/TestExprHelpExamples.py
@@ -19,7 +19,6 @@
self.line = line_number(self.main_source, '// Set breakpoint here.')
# rdar://problem/9673664
- @unittest2.expectedFailure
def test_expr_commands(self):
"""The following expression commands should just work."""
self.buildDefault()
@@ -35,9 +34,10 @@
# rdar://problem/9673664 lldb expression evaluation problem
- self.runCmd('expr char c[] = "foo"; c[0]')
- # Fill in an example output here.
- # And change self.runCmd() -> self.expect()...
+ self.expect('expr char c[] = "foo"; c[0]',
+ substrs = ["'f'"])
+ # runCmd: expr char c[] = "foo"; c[0]
+ # output: (char) $0 = 'f'
if __name__ == '__main__':