Disable the darwin_log tests as a category while we clean them up

[spyffe]

Summary

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.

[beanz]

This seems like a reasonable workaround until we can figure out a better solution. Thanks Sean!

lldb/trunk/packages/Python/lldbsuite/test/configuration.py

 # The test suite.
 suite = unittest2.TestSuite()
 
 # The list of categories we said we care about
 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 = {}
 
 # The path to LLDB.framework is optional.
 lldbFrameworkPath = None
 
 # Test suite repeat count.  Can be overwritten with '-# count'.
 count = 1

lldb/trunk/packages/Python/lldbsuite/test/functionalities/darwin_log/.categories

+darwin-log

lldb/trunk/packages/Python/lldbsuite/test/test_categories.py

all_categories = {
     'libc++': 'Test for libc++ data formatters',
     'objc': 'Tests related to the Objective-C programming language support',
     'pyapi': 'Tests related to the Python API',
     'basic_process': 'Basic process execution sniff tests.',
     'cmdline': 'Tests related to the LLDB command-line interface',
     '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):
     candidate = None
     for item in list:
         if not item.startswith(yourentry):
             continue
         if candidate: