If TestBase.expect() is passed an assert message, pass it along when delegating to TestBase.runCmd()

to execute the debugger command.  This will result in a more semantic assert message than just the
command failed message like before:

AssertionError: False is not True : Command 'thread list' returns successfully

And now, we will have:

AssertionError: False is not True : Process state is stopped due to breakpoint
llvm-svn: 117569

1 files changed, 1 insertions, 1 deletions

diff --git a/lldb/test/lldbtest.py b/lldb/test/lldbtest.py
index 7acd2c733ed..9b15f1bbf86 100644
--- a/lldb/test/lldbtest.py
+++ b/lldb/test/lldbtest.py
@@ -646,7 +646,7 @@ class TestBase(unittest2.TestCase):
 
         if exe:
             # First run the command.  If we are expecting error, set check=False.
-            self.runCmd(str, trace = (True if trace else False), check = not error)
+            self.runCmd(str, msg=msg, trace = (True if trace else False), check = not error)
 
             # Then compare the output against expected strings.
             output = self.res.GetError() if error else self.res.GetOutput()