<div dir="ltr"><div><div>Sorry, I take that back.  I forgot to save the buffer that ran the test script.  Oops :-(<br><br></div>I get a number of errors that make me think it's missing libc++, which makes sense because I never installed it.  However, I thought clang automatically falls back to using gcc's libstdc++.<br><br>Failures include:<br><br>Build Command Output:<br>main.cpp:10:10: fatal error: 'atomic' file not found<br>#include <atomic><br>         ^~~~~~~~<br>1 error generated.<br><br></div>and<br><br>Build Command Output:<br>main.cpp:1:10: fatal error: 'string' file not found<br>#include <string><br>         ^~~~~~~~<br>1 error generated.<br><br><div><div><div><br><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 20, 2017 at 11:30 AM, 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"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Thu, Apr 20, 2017 at 6:47 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">5. specifying gcc-4.8 instead of the locally compiled clang<br><br><div class="gmail_extra"><div class="gmail_quote"><span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>has most of the tests passing, with a handful of unexpected successes:<br><br>UNEXPECTED SUCCESS: TestRegisterVariables.Register<wbr>VariableTestCase.test_and_run_<wbr>command_dwarf (lang/c/register_variables/Tes<wbr>tRegisterVariables.py)<br>UNEXPECTED SUCCESS: TestRegisterVariables.Register<wbr>VariableTestCase.test_and_run_<wbr>command_dwo (lang/c/register_variables/Tes<wbr>tRegisterVariables.py)<br>UNEXPECTED SUCCESS: TestExitDuringBreak.ExitDuring<wbr>BreakpointTestCase.test_dwarf (functionalities/thread/exit_d<wbr>uring_break/TestExitDuringBrea<wbr>k.py)<br>UNEXPECTED SUCCESS: TestExitDuringBreak.ExitDuring<wbr>BreakpointTestCase.test_dwo (functionalities/thread/exit_d<wbr>uring_break/TestExitDuringBrea<wbr>k.py)<br>UNEXPECTED SUCCESS: TestThreadStates.ThreadStateTe<wbr>stCase.test_process_interrupt_<wbr>dwarf (functionalities/thread/state/<wbr>TestThreadStates.py)<br>UNEXPECTED SUCCESS: TestThreadStates.ThreadStateTe<wbr>stCase.test_process_interrupt_<wbr>dwo (functionalities/thread/state/<wbr>TestThreadStates.py)<br>UNEXPECTED SUCCESS: TestRaise.RaiseTestCase.test_r<wbr>estart_bug_dwarf (functionalities/signal/raise/<wbr>TestRaise.py)<br>UNEXPECTED SUCCESS: TestRaise.RaiseTestCase.test_r<wbr>estart_bug_dwo (functionalities/signal/raise/<wbr>TestRaise.py)<br>UNEXPECTED SUCCESS: TestMultithreaded.SBBreakpoint<wbr>CallbackCase.test_sb_api_liste<wbr>ner_resume_dwarf (api/multithreaded/TestMultith<wbr>readed.py)<br>UNEXPECTED SUCCESS: TestMultithreaded.SBBreakpoint<wbr>CallbackCase.test_sb_api_liste<wbr>ner_resume_dwo (api/multithreaded/TestMultith<wbr>readed.py)<br>UNEXPECTED SUCCESS: lldbsuite.test.lldbtest.TestPr<wbr>intf.test_with_dwarf (lang/cpp/printf/TestPrintf.py<wbr>)<br>UNEXPECTED SUCCESS: lldbsuite.test.lldbtest.TestPr<wbr>intf.test_with_dwo (lang/cpp/printf/TestPrintf.py<wbr>)<br></div></div></div></div></blockquote></span><div>The unexpected successes are expected, unfortunately. :) What happens here is that the tests are flaky and they fail like 1% of the time, so they are marked as xfail.</div></div></div></div></blockquote><div><br></div></span><div>Top of tree clang has the same set of unexpected successes.<br><br></div></div></div></div>
</blockquote></div><br></div>