The darwin_log tests are very fragile and currently do not properly assess the state of that functionality.
I have put them all in their own category, and made that category disabled by default. Differential revision: https://reviews.llvm.org/D31718 llvm-svn: 299587
This commit is contained in:
parent
03994b814d
commit
894c147104
|
@ -66,7 +66,7 @@ categoriesList = None
|
|||
# set to true if we are going to use categories for cherry-picking test cases
|
||||
useCategories = False
|
||||
# Categories we want to skip
|
||||
skipCategories = []
|
||||
skipCategories = ["darwin-log"]
|
||||
# use this to track per-category failures
|
||||
failuresPerCategory = {}
|
||||
|
||||
|
|
|
@ -0,0 +1 @@
|
|||
darwin-log
|
|
@ -33,7 +33,8 @@ all_categories = {
|
|||
'dyntype': 'Tests related to dynamic type support',
|
||||
'stresstest': 'Tests related to stressing lldb limits',
|
||||
'flakey': 'Flakey test cases, i.e. tests that do not reliably pass at each execution',
|
||||
'lldb-mi': 'lldb-mi tests'}
|
||||
'lldb-mi': 'lldb-mi tests',
|
||||
'darwin-log': 'Darwin log tests'}
|
||||
|
||||
|
||||
def unique_string_match(yourentry, list):
|
||||
|
|
Loading…
Reference in New Issue