From 8a93f822e1763b58a452107c58f925a1a61eb6ff Mon Sep 17 00:00:00 2001 From: Pavel Labath Date: Tue, 12 Jul 2016 15:07:18 +0000 Subject: [PATCH] [test] Fix category-based skipping Summary: LLDBTestResult.hardMarkAsSkipped marked the whole class as skipped when the first class in the test failed the category check. This meant that subsequent tests in the same class did not run even if they were passing the category filter. Fix that. Reviewers: tfiala Subscribers: lldb-commits Differential Revision: http://reviews.llvm.org/D22213 llvm-svn: 275173 --- lldb/packages/Python/lldbsuite/test/test_result.py | 2 -- 1 file changed, 2 deletions(-) diff --git a/lldb/packages/Python/lldbsuite/test/test_result.py b/lldb/packages/Python/lldbsuite/test/test_result.py index 3b4b0f4..01db1f69 100644 --- a/lldb/packages/Python/lldbsuite/test/test_result.py +++ b/lldb/packages/Python/lldbsuite/test/test_result.py @@ -113,8 +113,6 @@ class LLDBTestResult(unittest2.TextTestResult): def hardMarkAsSkipped(self,test): getattr(test, test._testMethodName).__func__.__unittest_skip__ = True getattr(test, test._testMethodName).__func__.__unittest_skip_why__ = "test case does not fall in any category of interest for this run" - test.__class__.__unittest_skip__ = True - test.__class__.__unittest_skip_why__ = "test case does not fall in any category of interest for this run" def startTest(self, test): if configuration.shouldSkipBecauseOfCategories(self.getCategoriesForTest(test)): -- 2.7.4