<div dir="ltr">Hmm I wonder if your lldb-server is able to attach to processes?  Siva, we used to have some kind of kernel flag or something that would allow attaching to a process that was launched by something else.  I don't recall exactly what it was off the top of my head, but I wonder if Zachary needs that?<div><br></div><div>-Todd</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 3, 2016 at 3:02 PM, Zachary Turner via lldb-dev <span dir="ltr"><<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">In my logs I'm seeing this:<div><br></div><div><div>UNSUPPORTED: LLDB (/usr/local/google_ssd/src/llvm/build/ninja_release/bin/clang-3.9-x86_64) :: test_inferior_print_exit_debugserver_dwo (TestLldbGdbServer.LldbGdbServerTestCase) (debugserver tests) </div><div>  File "/usr/local/google/home/zturner/ssd/src/llvm/tools/lldb/test/dotest.py", line 7, in <module></div><div>    lldbsuite.test.run_suite()</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/dotest.py", line 1089, in run_suite</div><div>    resultclass=test_result.LLDBTestResult).run(configuration.suite)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/runner.py", line 162, in run</div><div>    test(result)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/suite.py", line 65, in __call__</div><div>    return self.run(*args, **kwds)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/suite.py", line 85, in run</div><div>    self._wrapped_run(result)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/suite.py", line 115, in _wrapped_run</div><div>    test._wrapped_run(result, debug)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/suite.py", line 117, in _wrapped_run</div><div>    test(result)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/case.py", line 433, in __call__</div><div>    return self.run(*args, **kwds)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/case.py", line 361, in run</div><div>    success = self.runMethod(testMethod, result)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/case.py", line 391, in runMethod</div><div>    testMethod()</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py", line 1900, in dwarf_test_method</div><div>    return attrvalue(self)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/decorators.py", line 112, in wrapper</div><div>    func(*args, **kwargs)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestLldbGdbServer.py", line 250, in test_inferior_print_exit_llgs</div><div>    self.inferior_print_exit()</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestLldbGdbServer.py", line 237, in inferior_print_exit</div><div>    context = self.expect_gdbremote_sequence()</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-server/gdbremote_testcase.py", line 549, in expect_gdbremote_sequence</div><div>    return expect_lldb_gdbserver_replay(self, self.sock, self.test_sequence, timeout_seconds, self.logger)</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-server/lldbgdbserverutils.py", line 252, in expect_lldb_gdbserver_replay</div><div>    context["O_content"] = pump.get_accumulated_output()</div><div>  File "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-server/socket_packet_pump.py", line 81, in __exit__</div><div>    traceback.print_stack()</div><div>lldb-server exiting...</div><div><br></div><div>Could this be related to the timeout I'm seeing?  Has anyone seen this before?  It doesn't appear flaky, happens every time.</div><div><div class="h5"><br><div class="gmail_quote"><div dir="ltr">On Wed, Feb 3, 2016 at 2:57 PM Siva Chandra <<a href="mailto:sivachandra@google.com" target="_blank">sivachandra@google.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Our bot is running on Ubuntu 14.04 and is green:<br>
<a href="http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake" rel="noreferrer" target="_blank">http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake</a><br>
<br>
One thing though, the bot does not run the testsuite with clang-3.6.<br>
About the unexpected successes, they are very likely tests which were<br>
found to be flaky and marked as expectedFailure (or something similar)<br>
to keep the bot green. Even the bot logs show these unexpected<br>
successes.<br>
<br>
On Wed, Feb 3, 2016 at 2:50 PM, Zachary Turner via lldb-dev<br>
<<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br>
><br>
> On Linux I get the following test results:<br>
><br>
> UNEXPECTED SUCCESS: test_and_run_command_dwarf<br>
> (lang/c/const_variables/TestConstVariables.py)<br>
> UNEXPECTED SUCCESS: test_and_run_command_dwo<br>
> (lang/c/const_variables/TestConstVariables.py)<br>
> UNEXPECTED SUCCESS: test_command_script_immediate_output_dwarf<br>
> (functionalities/command_script_immediate_output/TestCommandScriptImmediateOutput.py)<br>
> UNEXPECTED SUCCESS: test_command_script_immediate_output_dwo<br>
> (functionalities/command_script_immediate_output/TestCommandScriptImmediateOutput.py)<br>
> UNEXPECTED SUCCESS: test_fd_leak_basic_dwarf<br>
> (functionalities/avoids-fd-leak/TestFdLeak.py)<br>
> UNEXPECTED SUCCESS: test_fd_leak_basic_dwo<br>
> (functionalities/avoids-fd-leak/TestFdLeak.py)<br>
> UNEXPECTED SUCCESS: test_fd_leak_log_dwarf<br>
> (functionalities/avoids-fd-leak/TestFdLeak.py)<br>
> UNEXPECTED SUCCESS: test_fd_leak_log_dwo<br>
> (functionalities/avoids-fd-leak/TestFdLeak.py)<br>
> UNEXPECTED SUCCESS: test_fd_leak_multitarget_dwarf<br>
> (functionalities/avoids-fd-leak/TestFdLeak.py)<br>
> UNEXPECTED SUCCESS: test_fd_leak_multitarget_dwo<br>
> (functionalities/avoids-fd-leak/TestFdLeak.py)<br>
> UNEXPECTED SUCCESS: test_file_scope_lookup_with_run_command_dwarf<br>
> (lang/cpp/namespace/TestNamespaceLookup.py)<br>
> UNEXPECTED SUCCESS: test_file_scope_lookup_with_run_command_dwo<br>
> (lang/cpp/namespace/TestNamespaceLookup.py)<br>
> UNEXPECTED SUCCESS: test_lldbmi_gdb_set_target_async_off<br>
> (tools/lldb-mi/TestMiGdbSetShow.py)<br>
> UNEXPECTED SUCCESS: test_lldbmi_process_output<br>
> (tools/lldb-mi/syntax/TestMiSyntax.py)<br>
> UNEXPECTED SUCCESS: test_lldbmi_settings_set_target_run_args_after<br>
> (tools/lldb-mi/interpreter/TestMiInterpreterExec.py)<br>
> UNEXPECTED SUCCESS: test_lldbmi_settings_set_target_run_args_before<br>
> (tools/lldb-mi/interpreter/TestMiInterpreterExec.py)<br>
> UNEXPECTED SUCCESS: test_restart_bug_dwarf<br>
> (functionalities/signal/raise/TestRaise.py)<br>
> UNEXPECTED SUCCESS: test_restart_bug_dwo<br>
> (functionalities/signal/raise/TestRaise.py)<br>
> UNEXPECTED SUCCESS: test_scope_lookup_before_using_with_run_command_dwo<br>
> (lang/cpp/namespace/TestNamespaceLookup.py)<br>
> TIMEOUT: test_qThreadInfo_matches_qC_attach_llgs_dwo<br>
> (tools/lldb-server/TestLldbGdbServer.py)<br>
> TIMEOUT: test_watchpoint_delay_watchpoint_one_breakpoint_dwarf<br>
> (functionalities/thread/concurrent_events/TestConcurrentEvents.py)<br>
><br>
><br>
> This is a ton of unexpected successes.  Does anyone regularly run the test<br>
> suite on Linux?  Is this normal?  I also notice that it takes almost 30<br>
> minutes to complete, and I get these timeouts:<br>
><br>
> TIMEOUT: test_qThreadInfo_matches_qC_attach_llgs_dwo<br>
> (tools/lldb-server/TestLldbGdbServer.py)<br>
> TIMEOUT: test_watchpoint_delay_watchpoint_one_breakpoint_dwarf<br>
> (functionalities/thread/concurrent_events/TestConcurrentEvents.py)<br>
><br>
> Are these known issues?  I'm using Ubuntu 14.04 and building tests with<br>
> Clang 3.6<br>
><br>
> _______________________________________________<br>
> lldb-dev mailing list<br>
> <a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a><br>
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br>
><br>
</blockquote></div></div></div></div></div>
<br>_______________________________________________<br>
lldb-dev mailing list<br>
<a href="mailto:lldb-dev@lists.llvm.org">lldb-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">-Todd</div></div>
</div>