summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/ScriptInterpreter/Python/PythonExceptionState.h
diff options
context:
space:
mode:
authorMichal Gorny <mgorny@gentoo.org>2019-02-12 18:09:00 +0000
committerMichal Gorny <mgorny@gentoo.org>2019-02-12 18:09:00 +0000
commitf6e5594e811c70986ad8af3aa3f9540fcb7a1149 (patch)
tree66326572e7118a7426ac2c8fcd358103d4375fac /lldb/source/Plugins/ScriptInterpreter/Python/PythonExceptionState.h
parent34bead750c25fb3fa56dfe268797c438b1ccbb66 (diff)
downloadbcm5719-llvm-f6e5594e811c70986ad8af3aa3f9540fcb7a1149.tar.gz
bcm5719-llvm-f6e5594e811c70986ad8af3aa3f9540fcb7a1149.zip
[lldb] [unittest] Avoid mixing '127.0.0.1' and 'localhost'
Fix the tests not to use '127.0.0.1' and 'localhost' interchangeably. More specifically, since tests bind specifically to 127.0.0.1, connect to that address as well; using 'localhost' can resolve to IPv6 address which can cause issues -- for example, if the matching port happens to be used by some other process, the tests hang forever waiting for the client to connect. While technically the case of randomly selected IPv4 port being taken on IPv6 loopback is not very likely, NetBSD happens to be suffering from some weird kernel issue where connection to that port succeeds nevertheless. Until we can really figure out what goes wrong there, this saves us from the tests hanging randomly. Differential Revision: https://reviews.llvm.org/D58131 llvm-svn: 353868
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/PythonExceptionState.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud