[lldb-dev] Running check-lldb

[Scott Smith via lldb-dev]

Sorry, I take that back.  I forgot to save the buffer that ran the test
script.  Oops :-(

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++.

Failures include:

Build Command Output:
main.cpp:10:10: fatal error: 'atomic' file not found
#include <atomic>
         ^~~~~~~~
1 error generated.

and

Build Command Output:
main.cpp:1:10: fatal error: 'string' file not found
#include <string>
         ^~~~~~~~
1 error generated.




On Thu, Apr 20, 2017 at 11:30 AM, Scott Smith <scott.smith at purestorage.com>
wrote:

> On Thu, Apr 20, 2017 at 6:47 AM, Pavel Labath <labath at google.com> wrote:
>
>> 5. specifying gcc-4.8 instead of the locally compiled clang
>>
>> has most of the tests passing, with a handful of unexpected successes:
>>>
>>> UNEXPECTED SUCCESS: TestRegisterVariables.Register
>>> VariableTestCase.test_and_run_command_dwarf
>>> (lang/c/register_variables/TestRegisterVariables.py)
>>> UNEXPECTED SUCCESS: TestRegisterVariables.Register
>>> VariableTestCase.test_and_run_command_dwo (lang/c/register_variables/Tes
>>> tRegisterVariables.py)
>>> UNEXPECTED SUCCESS: TestExitDuringBreak.ExitDuringBreakpointTestCase.test_dwarf
>>> (functionalities/thread/exit_during_break/TestExitDuringBreak.py)
>>> UNEXPECTED SUCCESS: TestExitDuringBreak.ExitDuringBreakpointTestCase.test_dwo
>>> (functionalities/thread/exit_during_break/TestExitDuringBreak.py)
>>> UNEXPECTED SUCCESS: TestThreadStates.ThreadStateTe
>>> stCase.test_process_interrupt_dwarf (functionalities/thread/state/
>>> TestThreadStates.py)
>>> UNEXPECTED SUCCESS: TestThreadStates.ThreadStateTe
>>> stCase.test_process_interrupt_dwo (functionalities/thread/state/
>>> TestThreadStates.py)
>>> UNEXPECTED SUCCESS: TestRaise.RaiseTestCase.test_restart_bug_dwarf
>>> (functionalities/signal/raise/TestRaise.py)
>>> UNEXPECTED SUCCESS: TestRaise.RaiseTestCase.test_restart_bug_dwo
>>> (functionalities/signal/raise/TestRaise.py)
>>> UNEXPECTED SUCCESS: TestMultithreaded.SBBreakpoint
>>> CallbackCase.test_sb_api_listener_resume_dwarf
>>> (api/multithreaded/TestMultithreaded.py)
>>> UNEXPECTED SUCCESS: TestMultithreaded.SBBreakpoint
>>> CallbackCase.test_sb_api_listener_resume_dwo
>>> (api/multithreaded/TestMultithreaded.py)
>>> UNEXPECTED SUCCESS: lldbsuite.test.lldbtest.TestPrintf.test_with_dwarf
>>> (lang/cpp/printf/TestPrintf.py)
>>> UNEXPECTED SUCCESS: lldbsuite.test.lldbtest.TestPrintf.test_with_dwo
>>> (lang/cpp/printf/TestPrintf.py)
>>>
>> 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.
>>
>
> Top of tree clang has the same set of unexpected successes.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20170420/44893319/attachment.html>