[lldb-dev] Problem running the test suite on Linux.

Todd Fiala via lldb-dev lldb-dev at lists.llvm.org
Wed Feb 3 15:05:33 PST 2016 

(Security around ptrace).

On Wed, Feb 3, 2016 at 3:04 PM, Todd Fiala <todd.fiala at gmail.com> wrote:

> 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?
>
> -Todd
>
> On Wed, Feb 3, 2016 at 3:02 PM, Zachary Turner via lldb-dev <
> lldb-dev at lists.llvm.org> wrote:
>
>> In my logs I'm seeing this:
>>
>> 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)
>>   File
>> "/usr/local/google/home/zturner/ssd/src/llvm/tools/lldb/test/dotest.py",
>> line 7, in <module>
>>     lldbsuite.test.run_suite()
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/dotest.py",
>> line 1089, in run_suite
>>     resultclass=test_result.LLDBTestResult).run(configuration.suite)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/runner.py",
>> line 162, in run
>>     test(result)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/suite.py",
>> line 65, in __call__
>>     return self.run(*args, **kwds)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/suite.py",
>> line 85, in run
>>     self._wrapped_run(result)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/suite.py",
>> line 115, in _wrapped_run
>>     test._wrapped_run(result, debug)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/suite.py",
>> line 117, in _wrapped_run
>>     test(result)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/case.py",
>> line 433, in __call__
>>     return self.run(*args, **kwds)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/case.py",
>> line 361, in run
>>     success = self.runMethod(testMethod, result)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/third_party/Python/module/unittest2/unittest2/case.py",
>> line 391, in runMethod
>>     testMethod()
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/lldbtest.py",
>> line 1900, in dwarf_test_method
>>     return attrvalue(self)
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/decorators.py",
>> line 112, in wrapper
>>     func(*args, **kwargs)
>>   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
>>     self.inferior_print_exit()
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestLldbGdbServer.py",
>> line 237, in inferior_print_exit
>>     context = self.expect_gdbremote_sequence()
>>   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
>>     return expect_lldb_gdbserver_replay(self, self.sock,
>> self.test_sequence, timeout_seconds, self.logger)
>>   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
>>     context["O_content"] = pump.get_accumulated_output()
>>   File
>> "/usr/local/google_ssd/src/llvm/tools/lldb/packages/Python/lldbsuite/test/tools/lldb-server/socket_packet_pump.py",
>> line 81, in __exit__
>>     traceback.print_stack()
>> lldb-server exiting...
>>
>> Could this be related to the timeout I'm seeing?  Has anyone seen this
>> before?  It doesn't appear flaky, happens every time.
>>
>> On Wed, Feb 3, 2016 at 2:57 PM Siva Chandra <sivachandra at google.com>
>> wrote:
>>
>>> Our bot is running on Ubuntu 14.04 and is green:
>>> http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake
>>>
>>> One thing though, the bot does not run the testsuite with clang-3.6.
>>> About the unexpected successes, they are very likely tests which were
>>> found to be flaky and marked as expectedFailure (or something similar)
>>> to keep the bot green. Even the bot logs show these unexpected
>>> successes.
>>>
>>> On Wed, Feb 3, 2016 at 2:50 PM, Zachary Turner via lldb-dev
>>> <lldb-dev at lists.llvm.org> wrote:
>>> >
>>> > On Linux I get the following test results:
>>> >
>>> > UNEXPECTED SUCCESS: test_and_run_command_dwarf
>>> > (lang/c/const_variables/TestConstVariables.py)
>>> > UNEXPECTED SUCCESS: test_and_run_command_dwo
>>> > (lang/c/const_variables/TestConstVariables.py)
>>> > UNEXPECTED SUCCESS: test_command_script_immediate_output_dwarf
>>> >
>>> (functionalities/command_script_immediate_output/TestCommandScriptImmediateOutput.py)
>>> > UNEXPECTED SUCCESS: test_command_script_immediate_output_dwo
>>> >
>>> (functionalities/command_script_immediate_output/TestCommandScriptImmediateOutput.py)
>>> > UNEXPECTED SUCCESS: test_fd_leak_basic_dwarf
>>> > (functionalities/avoids-fd-leak/TestFdLeak.py)
>>> > UNEXPECTED SUCCESS: test_fd_leak_basic_dwo
>>> > (functionalities/avoids-fd-leak/TestFdLeak.py)
>>> > UNEXPECTED SUCCESS: test_fd_leak_log_dwarf
>>> > (functionalities/avoids-fd-leak/TestFdLeak.py)
>>> > UNEXPECTED SUCCESS: test_fd_leak_log_dwo
>>> > (functionalities/avoids-fd-leak/TestFdLeak.py)
>>> > UNEXPECTED SUCCESS: test_fd_leak_multitarget_dwarf
>>> > (functionalities/avoids-fd-leak/TestFdLeak.py)
>>> > UNEXPECTED SUCCESS: test_fd_leak_multitarget_dwo
>>> > (functionalities/avoids-fd-leak/TestFdLeak.py)
>>> > UNEXPECTED SUCCESS: test_file_scope_lookup_with_run_command_dwarf
>>> > (lang/cpp/namespace/TestNamespaceLookup.py)
>>> > UNEXPECTED SUCCESS: test_file_scope_lookup_with_run_command_dwo
>>> > (lang/cpp/namespace/TestNamespaceLookup.py)
>>> > UNEXPECTED SUCCESS: test_lldbmi_gdb_set_target_async_off
>>> > (tools/lldb-mi/TestMiGdbSetShow.py)
>>> > UNEXPECTED SUCCESS: test_lldbmi_process_output
>>> > (tools/lldb-mi/syntax/TestMiSyntax.py)
>>> > UNEXPECTED SUCCESS: test_lldbmi_settings_set_target_run_args_after
>>> > (tools/lldb-mi/interpreter/TestMiInterpreterExec.py)
>>> > UNEXPECTED SUCCESS: test_lldbmi_settings_set_target_run_args_before
>>> > (tools/lldb-mi/interpreter/TestMiInterpreterExec.py)
>>> > UNEXPECTED SUCCESS: test_restart_bug_dwarf
>>> > (functionalities/signal/raise/TestRaise.py)
>>> > UNEXPECTED SUCCESS: test_restart_bug_dwo
>>> > (functionalities/signal/raise/TestRaise.py)
>>> > UNEXPECTED SUCCESS: test_scope_lookup_before_using_with_run_command_dwo
>>> > (lang/cpp/namespace/TestNamespaceLookup.py)
>>> > TIMEOUT: test_qThreadInfo_matches_qC_attach_llgs_dwo
>>> > (tools/lldb-server/TestLldbGdbServer.py)
>>> > TIMEOUT: test_watchpoint_delay_watchpoint_one_breakpoint_dwarf
>>> > (functionalities/thread/concurrent_events/TestConcurrentEvents.py)
>>> >
>>> >
>>> > This is a ton of unexpected successes.  Does anyone regularly run the
>>> test
>>> > suite on Linux?  Is this normal?  I also notice that it takes almost 30
>>> > minutes to complete, and I get these timeouts:
>>> >
>>> > TIMEOUT: test_qThreadInfo_matches_qC_attach_llgs_dwo
>>> > (tools/lldb-server/TestLldbGdbServer.py)
>>> > TIMEOUT: test_watchpoint_delay_watchpoint_one_breakpoint_dwarf
>>> > (functionalities/thread/concurrent_events/TestConcurrentEvents.py)
>>> >
>>> > Are these known issues?  I'm using Ubuntu 14.04 and building tests with
>>> > Clang 3.6
>>> >
>>> > _______________________________________________
>>> > lldb-dev mailing list
>>> > lldb-dev at lists.llvm.org
>>> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>> >
>>>
>>
>> _______________________________________________
>> lldb-dev mailing list
>> lldb-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>>
>
>
> --
> -Todd
>



-- 
-Todd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20160203/d0bb8051/attachment.html>

More information about the lldb-dev mailing list