3a6cc51cb9
Summary: This set of changes addresses the issue I described in [[ http://llvm.org/pr23403 | Bug 23403 ]], in short most LLDB-MI tests fail unexpectedly due to timeout on my Ubuntu 14.10 x86_64 VirtualBox VM. I have no idea why the Ubuntu buildbots don't seem to suffer from this issue. This patch just makes **MiTestCaseBase.spawnLldbMi()** block until the spawned LLDB-MI child process outputs the **(gdb)** prompt, which ensures that MI commands aren't sent to the LLDB-MI child process until it's ready. Before these changes 52 LLDB-MI tests failed unexpectedly (all but one due to timeouts), after these changes no tests fail due to timeouts. I still get one unexpected failure in **test_lldbmi_source_option_start_script_error** in **TestMiStartupOptions.py**, but that's due to a file error, that test should be skipped on Linux just like the other two //start_script// tests until the file error is fixed. Patch from Vadim Macagon. Thanks! Test Plan: ./dotest.py -A x86_64 -C clang --executable $BUILDDIR/bin/lldb tools/lldb-mi/ Reviewers: abidh, domipheus, ki.stfu Reviewed By: ki.stfu Subscribers: brucem, lldb-commits Differential Revision: http://reviews.llvm.org/D9595 llvm-svn: 236816
56 lines
2.0 KiB
Python
56 lines
2.0 KiB
Python
"""
|
|
Test that the lldb-mi driver prints prompt properly.
|
|
"""
|
|
|
|
import lldbmi_testcase
|
|
from lldbtest import *
|
|
import unittest2
|
|
|
|
class MiPromptTestCase(lldbmi_testcase.MiTestCaseBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
@lldbmi_test
|
|
@expectedFailureWindows("llvm.org/pr22274: need a pexpect replacement for windows")
|
|
@skipIfFreeBSD # llvm.org/pr22411: Failure presumably due to known thread races
|
|
def test_lldbmi_prompt(self):
|
|
"""Test that 'lldb-mi --interpreter' echos '(gdb)' after commands and events."""
|
|
|
|
self.spawnLldbMi(args = None)
|
|
|
|
# Test that lldb-mi is ready after unknown command
|
|
self.runCmd("-unknown-command")
|
|
self.expect("\^error,msg=\"Driver\. Received command '-unknown-command'\. It was not handled\. Command 'unknown-command' not in Command Factory\"")
|
|
self.expect(self.child_prompt, exactly = True)
|
|
|
|
# Test that lldb-mi is ready after -file-exec-and-symbols
|
|
self.runCmd("-file-exec-and-symbols %s" % self.myexe)
|
|
self.expect("\^done")
|
|
self.expect(self.child_prompt, exactly = True)
|
|
|
|
# Test that lldb-mi is ready after -break-insert
|
|
self.runCmd("-break-insert -f main")
|
|
self.expect("\^done,bkpt={number=\"1\"")
|
|
self.expect(self.child_prompt, exactly = True)
|
|
|
|
# Test that lldb-mi is ready after -exec-run
|
|
self.runCmd("-exec-run")
|
|
self.expect("\*running")
|
|
self.expect(self.child_prompt, exactly = True)
|
|
|
|
# Test that lldb-mi is ready after BP hit
|
|
self.expect("\*stopped,reason=\"breakpoint-hit\"")
|
|
self.expect(self.child_prompt, exactly = True)
|
|
|
|
# Test that lldb-mi is ready after -exec-continue
|
|
self.runCmd("-exec-continue")
|
|
self.expect("\^running")
|
|
self.expect(self.child_prompt, exactly = True)
|
|
|
|
# Test that lldb-mi is ready after program exited
|
|
self.expect("\*stopped,reason=\"exited-normally\"")
|
|
self.expect(self.child_prompt, exactly = True)
|
|
|
|
if __name__ == '__main__':
|
|
unittest2.main()
|