summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2017-10-23 23:15:37 +0000
committerPavel Labath <labath@google.com>2017-10-23 23:15:37 +0000
commitf877a0820c247bd2634883c2d957e239d267713b (patch)
treeffd83b529b03fdc6ec0f539c4d30544ed03ba845 /lldb/packages/Python/lldbsuite/test
parentdde92e58e4da30a29a89f5dae967153b958e02ed (diff)
downloadbcm5719-llvm-f877a0820c247bd2634883c2d957e239d267713b.tar.gz
bcm5719-llvm-f877a0820c247bd2634883c2d957e239d267713b.zip
Use ipv4 localhost address in lldb-server tests
Since the ipv6 patch, we've experienced occasional flakyness in lldb-server tests. This was due to the fact that lldb-server was trying to listen on both v4 and v6 localhost sockets (and consider it a success if at least one of them succeeded), while the test framework was only trying to connect to the v4 one. This change makes sure lldb-server only listens on the v4 socket. llvm-svn: 316391
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test')
-rw-r--r--lldb/packages/Python/lldbsuite/test/tools/lldb-server/gdbremote_testcase.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/packages/Python/lldbsuite/test/tools/lldb-server/gdbremote_testcase.py b/lldb/packages/Python/lldbsuite/test/tools/lldb-server/gdbremote_testcase.py
index 23cb8693585..67887256d97 100644
--- a/lldb/packages/Python/lldbsuite/test/tools/lldb-server/gdbremote_testcase.py
+++ b/lldb/packages/Python/lldbsuite/test/tools/lldb-server/gdbremote_testcase.py
@@ -369,7 +369,7 @@ class GdbRemoteTestCaseBase(TestBase):
["*:{}".format(self.port)]
else:
commandline_args = self.debug_monitor_extra_args + \
- ["localhost:{}".format(self.port)]
+ ["127.0.0.1:{}".format(self.port)]
if attach_pid:
commandline_args += ["--attach=%d" % attach_pid]
OpenPOWER on IntegriCloud