[Lldb-commits] [lldb] r263633 - Switch from unittest2.expectedFailure to our own decorator on TestSTL

[Pavel Labath via lldb-commits]

Author: labath
Date: Wed Mar 16 05:39:33 2016
New Revision: 263633

URL: http://llvm.org/viewvc/llvm-project?rev=263633&view=rev
Log:
Switch from unittest2.expectedFailure to our own decorator on TestSTL

the main reason is that our decorator contains extra fluff to "expect" crashes (which seem to
happen occasionaly on the android buildbot).

Modified:
    lldb/trunk/packages/Python/lldbsuite/test/lang/cpp/stl/TestSTL.py

Modified: lldb/trunk/packages/Python/lldbsuite/test/lang/cpp/stl/TestSTL.py
URL: http://llvm.org/viewvc/llvm-project/lldb/trunk/packages/Python/lldbsuite/test/lang/cpp/stl/TestSTL.py?rev=263633&r1=263632&r2=263633&view=diff
==============================================================================
--- lldb/trunk/packages/Python/lldbsuite/test/lang/cpp/stl/TestSTL.py (original)
+++ lldb/trunk/packages/Python/lldbsuite/test/lang/cpp/stl/TestSTL.py Wed Mar 16 05:39:33 2016
@@ -24,8 +24,7 @@ class STLTestCase(TestBase):
         self.source = 'main.cpp'
         self.line = line_number(self.source, '// Set break point at this line.')
 
-    # rdar://problem/10400981
-    @unittest2.expectedFailure
+    @expectedFailureAll(bugnumber="rdar://problem/10400981")
     def test(self):
         """Test some expressions involving STL data types."""
         self.build()