<div dir="ltr"><div><div><div><div><div><div><div>A combination of:<br></div><div>1. Updating to a known good release according to buildbot<br></div>2. using Ubuntu 14.04<br></div>3. compiling release using clang-4.0<br></div><div>4. using the dotest command line that buildbot uses<br></div>5. specifying gcc-4.8 instead of the locally compiled clang<br><br></div>has most of the tests passing, with a handful of unexpected successes:<br><br>UNEXPECTED SUCCESS: TestRegisterVariables.RegisterVariableTestCase.test_and_run_command_dwarf (lang/c/register_variables/TestRegisterVariables.py)<br>UNEXPECTED SUCCESS: TestRegisterVariables.RegisterVariableTestCase.test_and_run_command_dwo (lang/c/register_variables/TestRegisterVariables.py)<br>UNEXPECTED SUCCESS: TestExitDuringBreak.ExitDuringBreakpointTestCase.test_dwarf (functionalities/thread/exit_during_break/TestExitDuringBreak.py)<br>UNEXPECTED SUCCESS: TestExitDuringBreak.ExitDuringBreakpointTestCase.test_dwo (functionalities/thread/exit_during_break/TestExitDuringBreak.py)<br>UNEXPECTED SUCCESS: TestThreadStates.ThreadStateTestCase.test_process_interrupt_dwarf (functionalities/thread/state/TestThreadStates.py)<br>UNEXPECTED SUCCESS: TestThreadStates.ThreadStateTestCase.test_process_interrupt_dwo (functionalities/thread/state/TestThreadStates.py)<br>UNEXPECTED SUCCESS: TestRaise.RaiseTestCase.test_restart_bug_dwarf (functionalities/signal/raise/TestRaise.py)<br>UNEXPECTED SUCCESS: TestRaise.RaiseTestCase.test_restart_bug_dwo (functionalities/signal/raise/TestRaise.py)<br>UNEXPECTED SUCCESS: TestMultithreaded.SBBreakpointCallbackCase.test_sb_api_listener_resume_dwarf (api/multithreaded/TestMultithreaded.py)<br>UNEXPECTED SUCCESS: TestMultithreaded.SBBreakpointCallbackCase.test_sb_api_listener_resume_dwo (api/multithreaded/TestMultithreaded.py)<br>UNEXPECTED SUCCESS: lldbsuite.test.lldbtest.TestPrintf.test_with_dwarf (lang/cpp/printf/TestPrintf.py)<br>UNEXPECTED SUCCESS: lldbsuite.test.lldbtest.TestPrintf.test_with_dwo (lang/cpp/printf/TestPrintf.py)<br><br></div>This looks different than another user's issue: <a href="http://lists.llvm.org/pipermail/lldb-dev/2016-February/009504.html">http://lists.llvm.org/pipermail/lldb-dev/2016-February/009504.html</a><br><br></div>I also tried gcc-4.9.4 (via the ubuntu-toolchain-r ppa) and got a different set of problems:<br><br>FAIL: TestNamespaceDefinitions.NamespaceDefinitionsTestCase.test_expr_dwarf (lang/cpp/namespace_definitions/TestNamespaceDefinitions.py)<br>FAIL: TestNamespaceDefinitions.NamespaceDefinitionsTestCase.test_expr_dwo (lang/cpp/namespace_definitions/TestNamespaceDefinitions.py)<br>FAIL: TestTopLevelExprs.TopLevelExpressionsTestCase.test_top_level_expressions_dwarf (expression_command/top-level/TestTopLevelExprs.py)<br>FAIL: TestTopLevelExprs.TopLevelExpressionsTestCase.test_top_level_expressions_dwo (expression_command/top-level/TestTopLevelExprs.py)<br>UNEXPECTED SUCCESS: TestExitDuringBreak.ExitDuringBreakpointTestCase.test_dwarf (functionalities/thread/exit_during_break/TestExitDuringBreak.py)<br>UNEXPECTED SUCCESS: TestExitDuringBreak.ExitDuringBreakpointTestCase.test_dwo (functionalities/thread/exit_during_break/TestExitDuringBreak.py)<br>UNEXPECTED SUCCESS: TestThreadStates.ThreadStateTestCase.test_process_interrupt_dwarf (functionalities/thread/state/TestThreadStates.py)<br>UNEXPECTED SUCCESS: TestRaise.RaiseTestCase.test_restart_bug_dwarf (functionalities/signal/raise/TestRaise.py)<br>UNEXPECTED SUCCESS: TestRaise.RaiseTestCase.test_restart_bug_dwo (functionalities/signal/raise/TestRaise.py)<br>UNEXPECTED SUCCESS: TestMultithreaded.SBBreakpointCallbackCase.test_sb_api_listener_resume_dwarf (api/multithreaded/TestMultithreaded.py)<br>UNEXPECTED SUCCESS: TestMultithreaded.SBBreakpointCallbackCase.test_sb_api_listener_resume_dwo (api/multithreaded/TestMultithreaded.py)<br>UNEXPECTED SUCCESS: lldbsuite.test.lldbtest.TestPrintf.test_with_dwarf (lang/cpp/printf/TestPrintf.py)<br>UNEXPECTED SUCCESS: lldbsuite.test.lldbtest.TestPrintf.test_with_dwo (lang/cpp/printf/TestPrintf.py)<br><br></div>Well, at least the list is consistent, which gives me a base to start testing race conditions :-)<br><div><div><div><div><br><br></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 19, 2017 at 7:37 AM, Pavel Labath <span dir="ltr"><<a href="mailto:labath@google.com" target="_blank">labath@google.com</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">It is on purpose, although whether that purpose is worthwhile is debatable...<div><br></div><div>We chose to run release builds there so to align the bots closer to the binaries we release. Unfortunately, it does mean we run into situations like these...</div><div><br></div><div>In any case, I have now a patch up for fixing one of the crashers. The main one (assert during relocation processing) seems to be caused by a recent change in llvm. I am working towards identifying the cause, but that may take a while.</div><div><br></div><div>Then we can hopefully have a look at failures on your machine.</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On 19 April 2017 at 14:28, Scott Smith <span dir="ltr"><<a href="mailto:scott.smith@purestorage.com" target="_blank">scott.smith@purestorage.com</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">Yeah I found the buildbot instance for lldb on Ubuntu 14.04, but it looks like it is only running release builds. Is that on purpose?<br></div><div class="m_8451373276748302084HOEnZb"><div class="m_8451373276748302084h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 19, 2017 at 3:59 AM, Pavel Labath <span dir="ltr"><<a href="mailto:labath@google.com" target="_blank">labath@google.com</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">It looks like we are triggering an assert in llvm on a debug build. I'll try to track this down ASAP.<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_8451373276748302084m_8279548282185461816h5">On 18 April 2017 at 21:24, Scott Smith 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></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_8451373276748302084m_8279548282185461816h5"><div dir="ltr"><div><div><div><div>I'm trying to make sure some of my changes don't break lldb tests, but I'm having trouble getting a clean run even with a plain checkout.  I've tried the latest head of master, as well as release_40.  I'm running Ubuntu 16.04/amd64.  I built with:<br><br>cmake ../llvm -G Ninja -DCMAKE_BUILD_TYPE=Debug<br></div>ninja lldb<br></div>ninja check-lldb<br><br></div>Compiler is gcc-5.4, though I've also tried with clang-4.0.<br><br></div>Am I missing something obvious?  Is there a docker image / vm image / known good environments that I can use to reproduce a clean test run (on something Linux-y - sorry, I don't have a Mac)?<br><br></div>
<br></div></div>______________________________<wbr>_________________<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/<wbr>mailman/listinfo/lldb-dev</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>