summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/sbdata/TestSBData.py
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2018-12-20 20:44:23 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2018-12-20 20:44:23 +0000
commitdcc8fc9e985f16a6df878ec0ff7212e0a2da0c8f (patch)
treee66790e7035a5a7dbdd67ebfe3655cb80926a003 /lldb/packages/Python/lldbsuite/test/python_api/sbdata/TestSBData.py
parent3b7e8b2dbb1213d35917556f3e917d7add583506 (diff)
downloadbcm5719-llvm-dcc8fc9e985f16a6df878ec0ff7212e0a2da0c8f.tar.gz
bcm5719-llvm-dcc8fc9e985f16a6df878ec0ff7212e0a2da0c8f.zip
[dotest] Consider unexpected passes as failures.
Unexpected successes should be considered failures because they can hide regressions when not addressed. When a test is fixed and not re-enabled, it can easily regress without us noticing. I couldn't find a good way to make this change other than changing it in the unittest2 framework. I know this is less than optimal but since we have the dependency checked in and the change is pretty fundamental to the framework I think it's not unreasonable. Differential revision: https://reviews.llvm.org/D55835 llvm-svn: 349818
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/sbdata/TestSBData.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud