[lldb-dev] Problem with dotest_channels.py

[Zachary Turner via lldb-dev]

Hi Todd, lately I've been seeing this sporadically when running the test
suite.

[TestNamespaceLookup.py FAILED]
Command invoked: C:\Python27_LLDB\x86\python_d.exe
D:\src\llvm\tools\lldb\test\dotest.pyc -q --arch=i686 --executable
D:/src/llvmbuild/ninja/bin/lldb.exe -s
D:/src/llvmbuild/ninja/lldb-test-traces -u CXXFLAGS -u CFLAGS
--enable-crash-dialog -C d:\src\llvmbuild\ninja_release\bin\clang.exe
--results-port 55886 --inferior -p TestNamespaceLookup.py
D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test --event-add-entries
worker_index=10:int
416 out of 416 test suites processed - TestAddDsymCommand.py
    error: uncaptured python exception, closing channel
<lldbsuite.test.dotest_channels.UnpicklingForwardingReaderChannel connected
127.0.0.1:56008 at 0x2bdd578> (<class 'socket.error'>:[Errno 10054] An
existing connection was forcibly closed by the remote host
[C:\Python27_LLDB\x86\lib\asyncore.py|read|83]
[C:\Python27_LLDB\x86\lib\asyncore.py|handle_read_event|449]
[D:\src\llvm\tools\lldb\packages\Python\lldbsuite\test\dotest_channels.py|handle_read|133]
[C:\Python27_LLDB\x86\lib\asyncore.py|recv|387])

It seems to happen randomly and not always on the same test.  Sometimes it
doesn't happen at all.  I wonder if this could be related to some of the
work that's been going on recently.  Are you seeing this?  Any idea how to
diagnose?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20151214/a15fb8f1/attachment.html>