Re: [lldb-dev] [llvm-dev] [lit] check-all hanging
On Thu, Jan 3, 2019 at 11:30 AM Frédéric Riss wrote: > -llvm-dev + lldb-dev for the lldv test failures. > > On Jan 3, 2019, at 7:33 AM, Joel E. Denny wrote: > > All, > > Thanks for the replies. Kuba: For LLDB, when were things expected to have > improved? It's possible things improved for me at some point, but this > isn't something I've found time to track carefully, and I still see > problems. > > I ran check-all a couple of times last night at r350238, which I pulled > yesterday. Here are the results: > > ``` > > Testing Time: 5043.24s > > Unexpected Passing Tests (2): > lldb-Suite :: functionalities/asan/TestMemoryHistory.py > lldb-Suite :: functionalities/asan/TestReportData.py > > > Failing Tests (54): > Clang :: CXX/modules-ts/basic/basic.link/p2/module.cpp > Clang :: Modules/ExtDebugInfo.cpp > Clang :: Modules/using-directive-redecl.cpp > Clang :: Modules/using-directive.cpp > Clang :: PCH/chain-late-anonymous-namespace.cpp > Clang :: PCH/cxx-namespaces.cpp > Clang :: PCH/namespaces.cpp > LLDB :: ExecControl/StopHook/stop-hook-threads.test > LeakSanitizer-AddressSanitizer-x86_64 :: TestCases/Linux/ > use_tls_dynamic.cc > LeakSanitizer-Standalone-x86_64 :: TestCases/Linux/use_tls_dynamic.cc > MemorySanitizer-X86_64 :: dtls_test.c > MemorySanitizer-lld-X86_64 :: dtls_test.c > lldb-Suite :: > functionalities/register/register_command/TestRegisters.py > lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py > > > It’s hard to diagnose dotest failures without the log. > (My last reply to this was rejected by the list because I wasn't subscribed. Trying again.) I have no experience debugging lldb. Here's the lit output for the last fail (now at r350377), but let me know if you want something more: ``` FAIL: lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py (59083 of 59736) TEST 'lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py' FAILED lldb version 8.0.0 LLDB library dir: /home/jdenny/ornl/llvm-mono-git-build/bin LLDB import library dir: /home/jdenny/ornl/llvm-mono-git-build/bin Libc++ tests will not be run because: Unable to find libc++ installation Skipping following debug info categories: ['dsym', 'gmodules'] Session logs for test failures/errors/unexpected successes will go into directory '/home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces' Command invoked: /home/jdenny/ornl/llvm-mono-git/lldb/test/dotest.py -q --arch=x86_64 -s /home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces --build-dir /home/jdenny/ornl/llvm-mono-git-build/lldb-test-build.noindex -S nm -u CXXFLAGS -u CFLAGS --executable /home/jdenny/ornl/llvm-mono-git-build/./bin/lldb --dsymutil /home/jdenny/ornl/llvm-mono-git-build/./bin/dsymutil --filecheck /home/jdenny/ornl/llvm-mono-git-build/./bin/FileCheck -C /home/jdenny/ornl/llvm-mono-git-build/./bin/clang --env ARCHIVER=/usr/bin/ar --env OBJCOPY=/usr/bin/objcopy /home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/tools/lldb-server -p TestGdbRemoteRegisterState.py UNSUPPORTED: LLDB (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: test_grp_register_save_restore_works_no_suffix_debugserver (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) (debugserver tests) FAIL: LLDB (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: test_grp_register_save_restore_works_no_suffix_llgs (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) lldb-server exiting... UNSUPPORTED: LLDB (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: test_grp_register_save_restore_works_with_suffix_debugserver (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) (debugserver tests) FAIL: LLDB (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: test_grp_register_save_restore_works_with_suffix_llgs (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) lldb-server exiting... == FAIL: test_grp_register_save_restore_works_no_suffix_llgs (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) -- Traceback (most recent call last): File "/home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/decorators.py", line 144, in wrapper func(*args, **kwargs) File "/home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestGdbRemoteRegisterState.py", line 137, in test_grp_register_save_restore_works_no_suffix_llgs self.grp_register_save_restore_works(USE_THREAD_SUFFIX) File "/home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestGdbRemoteRegisterState.py", line 97, in grp_register_save_restore_works context = self.expect_gdbremote_sequence() File "/home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/tools/lldb-s
Re: [lldb-dev] [llvm-dev] [lit] check-all hanging
On Fri, Jan 4, 2019 at 11:39 AM Frédéric Riss wrote: > > > > On Jan 4, 2019, at 7:30 AM, Joel E. Denny wrote: > > > > On Thu, Jan 3, 2019 at 11:30 AM Frédéric Riss wrote: > > -llvm-dev + lldb-dev for the lldv test failures. > > > >> On Jan 3, 2019, at 7:33 AM, Joel E. Denny > wrote: > >> > >> All, > >> > >> Thanks for the replies. Kuba: For LLDB, when were things expected to > have improved? It's possible things improved for me at some point, but > this isn't something I've found time to track carefully, and I still see > problems. > >> > >> I ran check-all a couple of times last night at r350238, which I pulled > yesterday. Here are the results: > >> > >> ``` > >> > >> Testing Time: 5043.24s > >> > >> Unexpected Passing Tests (2): > >> lldb-Suite :: functionalities/asan/TestMemoryHistory.py > >> lldb-Suite :: functionalities/asan/TestReportData.py > >> > >> > >> Failing Tests (54): > >> Clang :: CXX/modules-ts/basic/basic.link/p2/module.cpp > >> Clang :: Modules/ExtDebugInfo.cpp > >> Clang :: Modules/using-directive-redecl.cpp > >> Clang :: Modules/using-directive.cpp > >> Clang :: PCH/chain-late-anonymous-namespace.cpp > >> Clang :: PCH/cxx-namespaces.cpp > >> Clang :: PCH/namespaces.cpp > >> LLDB :: ExecControl/StopHook/stop-hook-threads.test > >> LeakSanitizer-AddressSanitizer-x86_64 :: > TestCases/Linux/use_tls_dynamic.cc > >> LeakSanitizer-Standalone-x86_64 :: > TestCases/Linux/use_tls_dynamic.cc > >> MemorySanitizer-X86_64 :: dtls_test.c > >> MemorySanitizer-lld-X86_64 :: dtls_test.c > >> lldb-Suite :: > functionalities/register/register_command/TestRegisters.py > >> lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py > > > > It’s hard to diagnose dotest failures without the log. > > > > (My last reply to this was rejected by the list because I wasn't > subscribed. Trying again.) > > > > I have no experience debugging lldb. Here's the lit output for the last > fail (now at r350377), but let me know if you want something more: > > > > ``` > > FAIL: lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py > (59083 of 59736) > > TEST 'lldb-Suite :: > tools/lldb-server/TestGdbRemoteRegisterState.py' FAILED > > lldb version 8.0.0 > > LLDB library dir: /home/jdenny/ornl/llvm-mono-git-build/bin > > LLDB import library dir: /home/jdenny/ornl/llvm-mono-git-build/bin > > Libc++ tests will not be run because: Unable to find libc++ installation > > Skipping following debug info categories: ['dsym', 'gmodules'] > > > > Session logs for test failures/errors/unexpected successes will go into > directory '/home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces' > > Command invoked: /home/jdenny/ornl/llvm-mono-git/lldb/test/dotest.py -q > --arch=x86_64 -s /home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces > --build-dir /home/jdenny/ornl/llvm-mono-git-build/lldb-test-build.noindex > -S nm -u CXXFLAGS -u CFLAGS --executable > /home/jdenny/ornl/llvm-mono-git-build/./bin/lldb --dsymutil > /home/jdenny/ornl/llvm-mono-git-build/./bin/dsymutil --filecheck > /home/jdenny/ornl/llvm-mono-git-build/./bin/FileCheck -C > /home/jdenny/ornl/llvm-mono-git-build/./bin/clang --env > ARCHIVER=/usr/bin/ar --env OBJCOPY=/usr/bin/objcopy > /home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/tools/lldb-server > -p TestGdbRemoteRegisterState.py > > UNSUPPORTED: LLDB > (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: > test_grp_register_save_restore_works_no_suffix_debugserver > (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) (debugserver tests) > > FAIL: LLDB (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: > test_grp_register_save_restore_works_no_suffix_llgs > (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) > > lldb-server exiting... > > UNSUPPORTED: LLDB > (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: > test_grp_register_save_restore_works_with_suffix_debugserver > (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) (debugserver tests) > > FAIL: LLDB (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: > test_grp_register_save_restore_works_with_suffix_llgs > (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) > > lldb-server exiting... > > == > > FAIL: test_grp_register_save_restore_works_no_suffix_llgs > (TestGdbRemoteRegisterState.TestGdbRemoteRegisterState) > > -- > > Traceback (most recent call last): > > File > "/home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/decorators.py", > line 144, in wrapper > > func(*args, **kwargs) > > File > "/home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/tools/lldb-server/TestGdbRemoteRegisterState.py", > line 137, in test_grp_register_save
Re: [lldb-dev] [llvm-dev] [lit] check-all hanging
On Mon, Jan 7, 2019 at 11:15 AM Davide Italiano wrote: > On Sat, Jan 5, 2019 at 9:48 AM Joel E. Denny via lldb-dev > wrote: > > > > On Fri, Jan 4, 2019 at 11:39 AM Frédéric Riss wrote: > >> > >> > >> > >> > On Jan 4, 2019, at 7:30 AM, Joel E. Denny > wrote: > >> > > >> > On Thu, Jan 3, 2019 at 11:30 AM Frédéric Riss > wrote: > >> > -llvm-dev + lldb-dev for the lldv test failures. > >> > > >> >> On Jan 3, 2019, at 7:33 AM, Joel E. Denny > wrote: > >> >> > >> >> All, > >> >> > >> >> Thanks for the replies. Kuba: For LLDB, when were things expected > to have improved? It's possible things improved for me at some point, but > this isn't something I've found time to track carefully, and I still see > problems. > >> >> > >> >> I ran check-all a couple of times last night at r350238, which I > pulled yesterday. Here are the results: > >> >> > >> >> ``` > >> >> > >> >> Testing Time: 5043.24s > >> >> > >> >> Unexpected Passing Tests (2): > >> >> lldb-Suite :: functionalities/asan/TestMemoryHistory.py > >> >> lldb-Suite :: functionalities/asan/TestReportData.py > >> >> > >> >> > >> >> Failing Tests (54): > >> >> Clang :: CXX/modules-ts/basic/basic.link/p2/module.cpp > >> >> Clang :: Modules/ExtDebugInfo.cpp > >> >> Clang :: Modules/using-directive-redecl.cpp > >> >> Clang :: Modules/using-directive.cpp > >> >> Clang :: PCH/chain-late-anonymous-namespace.cpp > >> >> Clang :: PCH/cxx-namespaces.cpp > >> >> Clang :: PCH/namespaces.cpp > >> >> LLDB :: ExecControl/StopHook/stop-hook-threads.test > >> >> LeakSanitizer-AddressSanitizer-x86_64 :: > TestCases/Linux/use_tls_dynamic.cc > >> >> LeakSanitizer-Standalone-x86_64 :: > TestCases/Linux/use_tls_dynamic.cc > >> >> MemorySanitizer-X86_64 :: dtls_test.c > >> >> MemorySanitizer-lld-X86_64 :: dtls_test.c > >> >> lldb-Suite :: > functionalities/register/register_command/TestRegisters.py > >> >> lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py > >> > > >> > It’s hard to diagnose dotest failures without the log. > >> > > >> > (My last reply to this was rejected by the list because I wasn't > subscribed. Trying again.) > >> > > >> > I have no experience debugging lldb. Here's the lit output for the > last fail (now at r350377), but let me know if you want something more: > >> > > >> > ``` > >> > FAIL: lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py > (59083 of 59736) > >> > TEST 'lldb-Suite :: > tools/lldb-server/TestGdbRemoteRegisterState.py' FAILED > >> > lldb version 8.0.0 > >> > LLDB library dir: /home/jdenny/ornl/llvm-mono-git-build/bin > >> > LLDB import library dir: /home/jdenny/ornl/llvm-mono-git-build/bin > >> > Libc++ tests will not be run because: Unable to find libc++ > installation > >> > Skipping following debug info categories: ['dsym', 'gmodules'] > >> > > >> > Session logs for test failures/errors/unexpected successes will go > into directory '/home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces' > >> > Command invoked: /home/jdenny/ornl/llvm-mono-git/lldb/test/dotest.py > -q --arch=x86_64 -s /home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces > --build-dir /home/jdenny/ornl/llvm-mono-git-build/lldb-test-build.noindex > -S nm -u CXXFLAGS -u CFLAGS --executable > /home/jdenny/ornl/llvm-mono-git-build/./bin/lldb --dsymutil > /home/jdenny/ornl/llvm-mono-git-build/./bin/dsymutil --filecheck > /home/jdenny/ornl/llvm-mono-git-build/./bin/FileCheck -C > /home/jdenny/ornl/llvm-mono-git-build/./bin/clang --env > ARCHIVER=/usr/bin/ar --env OBJCOPY=/usr/bin/objcopy > /home/jdenny/ornl/llvm-mono-git/lldb/packages/Python/lldbsuite/test/tools/lldb-server > -p TestGdbRemoteRegisterState.py > >> > UNSUPPORTED: LLDB > (/home/jdenny/ornl/llvm-mono-git-build/bin/clang-8-x86_64) :: > test_grp_register_save_restore_works_no_suffix_deb
Re: [lldb-dev] [llvm-dev] [lit] check-all hanging
On Mon, Jan 7, 2019 at 11:39 AM Adrian Prantl wrote: > > > On Jan 7, 2019, at 8:28 AM, Joel E. Denny via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > > On Mon, Jan 7, 2019 at 11:15 AM Davide Italiano > wrote: > >> On Sat, Jan 5, 2019 at 9:48 AM Joel E. Denny via lldb-dev >> wrote: >> > >> > On Fri, Jan 4, 2019 at 11:39 AM Frédéric Riss wrote: >> >> >> >> >> >> >> >> > On Jan 4, 2019, at 7:30 AM, Joel E. Denny >> wrote: >> >> > >> >> > On Thu, Jan 3, 2019 at 11:30 AM Frédéric Riss >> wrote: >> >> > -llvm-dev + lldb-dev for the lldv test failures. >> >> > >> >> >> On Jan 3, 2019, at 7:33 AM, Joel E. Denny >> wrote: >> >> >> >> >> >> All, >> >> >> >> >> >> Thanks for the replies. Kuba: For LLDB, when were things expected >> to have improved? It's possible things improved for me at some point, but >> this isn't something I've found time to track carefully, and I still see >> problems. >> >> >> >> >> >> I ran check-all a couple of times last night at r350238, which I >> pulled yesterday. Here are the results: >> >> >> >> >> >> ``` >> >> >> >> >> >> Testing Time: 5043.24s >> >> >> >> >> >> Unexpected Passing Tests (2): >> >> >> lldb-Suite :: functionalities/asan/TestMemoryHistory.py >> >> >> lldb-Suite :: functionalities/asan/TestReportData.py >> >> >> >> >> >> >> >> >> Failing Tests (54): >> >> >> Clang :: CXX/modules-ts/basic/basic.link/p2/module.cpp >> >> >> Clang :: Modules/ExtDebugInfo.cpp >> >> >> Clang :: Modules/using-directive-redecl.cpp >> >> >> Clang :: Modules/using-directive.cpp >> >> >> Clang :: PCH/chain-late-anonymous-namespace.cpp >> >> >> Clang :: PCH/cxx-namespaces.cpp >> >> >> Clang :: PCH/namespaces.cpp >> >> >> LLDB :: ExecControl/StopHook/stop-hook-threads.test >> >> >> LeakSanitizer-AddressSanitizer-x86_64 :: TestCases/Linux/ >> use_tls_dynamic.cc >> >> >> LeakSanitizer-Standalone-x86_64 :: TestCases/Linux/ >> use_tls_dynamic.cc >> >> >> MemorySanitizer-X86_64 :: dtls_test.c >> >> >> MemorySanitizer-lld-X86_64 :: dtls_test.c >> >> >> lldb-Suite :: >> functionalities/register/register_command/TestRegisters.py >> >> >> lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py >> >> > >> >> > It’s hard to diagnose dotest failures without the log. >> >> > >> >> > (My last reply to this was rejected by the list because I wasn't >> subscribed. Trying again.) >> >> > >> >> > I have no experience debugging lldb. Here's the lit output for the >> last fail (now at r350377), but let me know if you want something more: >> >> > >> >> > ``` >> >> > FAIL: lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py >> (59083 of 59736) >> >> > TEST 'lldb-Suite :: >> tools/lldb-server/TestGdbRemoteRegisterState.py' FAILED >> >> > lldb version 8.0.0 >> >> > LLDB library dir: /home/jdenny/ornl/llvm-mono-git-build/bin >> >> > LLDB import library dir: /home/jdenny/ornl/llvm-mono-git-build/bin >> >> > Libc++ tests will not be run because: Unable to find libc++ >> installation >> >> > Skipping following debug info categories: ['dsym', 'gmodules'] >> >> > >> >> > Session logs for test failures/errors/unexpected successes will go >> into directory '/home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces' >> >> > Command invoked: /home/jdenny/ornl/llvm-mono-git/lldb/test/dotest.py >> -q --arch=x86_64 -s /home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces >> --build-dir /home/jdenny/ornl/llvm-mono-git-build/lldb-test-build.noindex >> -S nm -u CXXFLAGS -u CFLAGS --executable >> /home/jdenny/ornl/llvm-mono-git-build/./bin/lldb --dsymutil >> /home/jdenny/ornl/llvm-mono-git-build/./bin/dsymutil --filecheck >> /hom
Re: [lldb-dev] [llvm-dev] [lit] check-all hanging
On Mon, Jan 7, 2019 at 9:08 PM Joel E. Denny wrote: > On Mon, Jan 7, 2019 at 11:39 AM Adrian Prantl wrote: > >> >> >> On Jan 7, 2019, at 8:28 AM, Joel E. Denny via lldb-dev < >> lldb-dev@lists.llvm.org> wrote: >> >> On Mon, Jan 7, 2019 at 11:15 AM Davide Italiano >> wrote: >> >>> On Sat, Jan 5, 2019 at 9:48 AM Joel E. Denny via lldb-dev >>> wrote: >>> > >>> > On Fri, Jan 4, 2019 at 11:39 AM Frédéric Riss wrote: >>> >> >>> >> >>> >> >>> >> > On Jan 4, 2019, at 7:30 AM, Joel E. Denny >>> wrote: >>> >> > >>> >> > On Thu, Jan 3, 2019 at 11:30 AM Frédéric Riss >>> wrote: >>> >> > -llvm-dev + lldb-dev for the lldv test failures. >>> >> > >>> >> >> On Jan 3, 2019, at 7:33 AM, Joel E. Denny >>> wrote: >>> >> >> >>> >> >> All, >>> >> >> >>> >> >> Thanks for the replies. Kuba: For LLDB, when were things expected >>> to have improved? It's possible things improved for me at some point, but >>> this isn't something I've found time to track carefully, and I still see >>> problems. >>> >> >> >>> >> >> I ran check-all a couple of times last night at r350238, which I >>> pulled yesterday. Here are the results: >>> >> >> >>> >> >> ``` >>> >> >> >>> >> >> Testing Time: 5043.24s >>> >> >> >>> >> >> Unexpected Passing Tests (2): >>> >> >> lldb-Suite :: functionalities/asan/TestMemoryHistory.py >>> >> >> lldb-Suite :: functionalities/asan/TestReportData.py >>> >> >> >>> >> >> >>> >> >> Failing Tests (54): >>> >> >> Clang :: CXX/modules-ts/basic/basic.link/p2/module.cpp >>> >> >> Clang :: Modules/ExtDebugInfo.cpp >>> >> >> Clang :: Modules/using-directive-redecl.cpp >>> >> >> Clang :: Modules/using-directive.cpp >>> >> >> Clang :: PCH/chain-late-anonymous-namespace.cpp >>> >> >> Clang :: PCH/cxx-namespaces.cpp >>> >> >> Clang :: PCH/namespaces.cpp >>> >> >> LLDB :: ExecControl/StopHook/stop-hook-threads.test >>> >> >> LeakSanitizer-AddressSanitizer-x86_64 :: TestCases/Linux/ >>> use_tls_dynamic.cc >>> >> >> LeakSanitizer-Standalone-x86_64 :: TestCases/Linux/ >>> use_tls_dynamic.cc >>> >> >> MemorySanitizer-X86_64 :: dtls_test.c >>> >> >> MemorySanitizer-lld-X86_64 :: dtls_test.c >>> >> >> lldb-Suite :: >>> functionalities/register/register_command/TestRegisters.py >>> >> >> lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py >>> >> > >>> >> > It’s hard to diagnose dotest failures without the log. >>> >> > >>> >> > (My last reply to this was rejected by the list because I wasn't >>> subscribed. Trying again.) >>> >> > >>> >> > I have no experience debugging lldb. Here's the lit output for the >>> last fail (now at r350377), but let me know if you want something more: >>> >> > >>> >> > ``` >>> >> > FAIL: lldb-Suite :: tools/lldb-server/TestGdbRemoteRegisterState.py >>> (59083 of 59736) >>> >> > TEST 'lldb-Suite :: >>> tools/lldb-server/TestGdbRemoteRegisterState.py' FAILED >>> >> > lldb version 8.0.0 >>> >> > LLDB library dir: /home/jdenny/ornl/llvm-mono-git-build/bin >>> >> > LLDB import library dir: /home/jdenny/ornl/llvm-mono-git-build/bin >>> >> > Libc++ tests will not be run because: Unable to find libc++ >>> installation >>> >> > Skipping following debug info categories: ['dsym', 'gmodules'] >>> >> > >>> >> > Session logs for test failures/errors/unexpected successes will go >>> into directory '/home/jdenny/ornl/llvm-mono-git-build/lldb-test-traces' >>> >> > Command invoked: >>> /home/jdenny/ornl/llvm-mono-g
