[Lldb-commits] [lldb] r118252 - /lldb/trunk/test/forward/TestForwardDeclaration.py

Johnny Chen johnny.chen at apple.com
Thu Nov 4 10:37:20 PDT 2010


Author: johnny
Date: Thu Nov  4 12:37:20 2010
New Revision: 118252

URL: http://llvm.org/viewvc/llvm-project?rev=118252&view=rev
Log:
Add one @skip decorator for assertion abort:

    @unittest2.skip("rdar://problem/8630601 Assertion failed: (result_valobj_sp.get()), function EvaluateExpression, file CommandObjectExpression.cpp, line 227.")

Modified:
    lldb/trunk/test/forward/TestForwardDeclaration.py

Modified: lldb/trunk/test/forward/TestForwardDeclaration.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/test/forward/TestForwardDeclaration.py?rev=118252&r1=118251&r2=118252&view=diff
==============================================================================
--- lldb/trunk/test/forward/TestForwardDeclaration.py (original)
+++ lldb/trunk/test/forward/TestForwardDeclaration.py Thu Nov  4 12:37:20 2010
@@ -9,12 +9,15 @@
 
     mydir = "forward"
 
+    @unittest2.skip("rdar://problem/8630601 Assertion failed: (result_valobj_sp.get()), function EvaluateExpression, file CommandObjectExpression.cpp, line 227.")
     @unittest2.skipUnless(sys.platform.startswith("darwin"), "requires Darwin")
     def test_with_dsym_and_run_command(self):
         """Display *bar_ptr when stopped on a function with forward declaration of struct bar."""
         self.buildDsym()
         self.forward_declaration()
 
+    # The expected failure happens before the assert, so there's no need to @skip.
+    #@unittest2.skip("rdar://problem/8630601 Assertion failed: (result_valobj_sp.get()), function EvaluateExpression, file CommandObjectExpression.cpp, line 227.")
     # rdar://problem/8546815
     # './dotest.py -v -t forward' fails for test_with_dwarf_and_run_command
     @unittest2.expectedFailure





More information about the lldb-commits mailing list