Add @expectedFailure for TestCallStdStringFunction.py (radar was filed) and

remove @expectedFailure from TestObjCMethods.py's print_ivars_correctly()
function (it has been passing for a while).

llvm-svn: 134022

lldb/test/expression_command/call-function/TestCallStdStringFunction.py

@@ -18,14 +18,16 @@ class ExprCommandCallFunctionTestCase(TestBase):
         self.line = line_number('main.cpp',
                                 '// Please test these expressions while stopped at this line:')
 
+    # rdar://problem/9471744 test failure: ./dotest.py -C clang -v -w -t -p CallStdString
+    @unittest2.expectedFailure
     @unittest2.skipUnless(sys.platform.startswith("darwin"), "requires Darwin")
     def test_with_dsym(self):
         """Test calling std::String member function."""
         self.buildDsym()
         self.call_function()
 
-    @unittest2.skipUnless(sys.platform.startswith("darwin"), "requires Darwin")
-    @python_api_test
+    # rdar://problem/9471744 test failure: ./dotest.py -C clang -v -w -t -p CallStdString
+    @unittest2.expectedFailure
     def test_with_dwarf_(self):
         """Test calling std::String member function."""
         self.buildDsym()

lldb/test/lang/objc/foundation/TestObjCMethods.py

@@ -199,7 +199,6 @@ class FoundationTestCase(TestBase):
         self.expect("expression -o -- my", "Object description displayed correctly",
             patterns = ["Hello from.*a.out.*with timestamp: "])
 
-    @unittest2.expectedFailure
     # See: <rdar://problem/8717050> lldb needs to use the ObjC runtime symbols for ivar offsets
     # Only fails for the ObjC 2.0 runtime.
     def print_ivars_correctly(self) :