summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lldbtest.py
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/lldbtest.py
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/lldbtest.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud