Re: [lldb-dev] [ASTImporter][macOS] Cannot link debugserver, keychain error
Hi Gabor Is this behavior reproducible with the current upstream LLDB? (after https://reviews.llvm.org/D55013) Did you follow the instructions in docs/code-signing.txt? > There is a setting to disable it. These days, you should be able to achieve > it with LLDB_CODESIGN_IDENTITY="" or SKIP_DEBUGSERVER=ON, though that may > change in the future (/me points at Stefan). My changes that landed last week kept the default behavior intact: build debugserver from source and code sign with lldb_codesign. In order to change this you can configure with: * -DLLDB_USE_SYSTEM_DEBUGSERVER=ON to use a copy of the system's debugserver instead * -DLLDB_NO_DEBUGSERVER=ON to have no debugserver at all Best Stefan > On 10. Dec 2018, at 20:28, Gábor Márton via lldb-dev > wrote: > > Hi, > > Recently I have updated the LLDB source and now I cannot link the debugserver. > I guess, the problem is started in one of the commits at last week, because > before that I had not experienced it. > Any help would be appreciated. I'd like to get a command line only solution > because I am building via ssh, so I can't click on any windows. > With respect to Clang/ASTImporter, > would it be a solution to disable the build of the debugserver and use the > system debugserver? Do you think I would loose some ASTImporter related test > coverage? How to disable the build of the debugserver? > > Thanks, > Gabor > > [4/172] Linking CXX executable bin/debugserver > FAILED: bin/debugserver > : && /usr/local/opt/ccache/libexec/c++ -fPIC -fvisibility-inlines-hidden > -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -fmodules > -fmodules-cache-path=/Users/egbomrt/llvm/build/release_assert/module.cache > -fcxx-modules -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual > -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough > -Wcovered-switch-default -Wno-noexcept-type -Wnon-virtual-dtor > -Wdelete-non-virtual-dtor -Wstring-conversion -fdiagnostics-color > -Wno-deprecated-declarations -Wno-unknown-pragmas -Wno-strict-aliasing > -Wno-deprecated-register -Wno-vla-extension > -Wno-gnu-zero-variadic-macro-arguments -Wno-zero-length-array > -Wno-extended-offsetof -O3 -isysroot > /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk > -Wl,-search_paths_first -Wl,-headerpad_max_install_names -stdlib=libc++ > -Wl,-sectcreate,__TEXT,__info_plist,/Users/egbomrt/llvm/git/llvm/tools/lldb/tools/debugserver/source/../resources/lldb-debugserver-Info.plist > -Wl,-dead_strip > tools/lldb/tools/debugserver/source/CMakeFiles/debugserver.dir/debugserver.cpp.o > -o bin/debugserver -Wl,-rpath,@loader_path/../lib > lib/liblldbDebugserverCommon.a -framework Cocoa -framework CoreFoundation > -framework Foundation lib/liblldbDebugserverArchSupport.a > lib/liblldbDebugserverDarwin_DarwinLog.a -lcompression && cd > /Users/egbomrt/llvm/build/release_assert/tools/lldb/tools/debugserver/source > && /usr/local/Cellar/cmake/3.12.4/bin/cmake -E env > CODESIGN_ALLOCATE=/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/codesign_allocate > codesign --force --sign lldb_codesign --entitlements > /Users/egbomrt/llvm/git/llvm/tools/lldb/tools/debugserver/source/../../../resources/debugserver-macosx-entitlements.plist > /Users/egbomrt/llvm/build/release_assert/bin/debugserver > error: The specified item could not be found in the keychain. > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] LLDB bot health
Inspired by people recently asking about or filing bugs for test fails that happen in their own environments, I thought I might do the same. "But wait," I thought, "maybe some bots are already finding these." Which led me to discover: lldb-amd64-ninja-netbsd8 green lldb-windows7-androidtest failures lldb-x64-windows-ninja test failures lldb-x86-windows-msvc2015out of disk space lldb-x86_64-darwin-13.4 cmake errors lldb-x86_64-ubuntu-14.04-android cmake errors lldb-x86_64-ubuntu-14.04-buildserver green lldb-x86_64-ubuntu-14.04-cmake test failures So, the bots aren't really all that healthy, and three of them have some sort of apparent configuration issue. Doesn't seem worth my while to report my personal failure list in this kind of environment. Just sayin'. --paulr ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLDB bot health
On Fri, Jan 11, 2019 at 9:20 AM via lldb-dev wrote: > > Inspired by people recently asking about or filing bugs for test fails > that happen in their own environments, I thought I might do the same. > "But wait," I thought, "maybe some bots are already finding these." > > Which led me to discover: > > lldb-amd64-ninja-netbsd8 green > lldb-windows7-androidtest failures > lldb-x64-windows-ninja test failures > lldb-x86-windows-msvc2015out of disk space > lldb-x86_64-darwin-13.4 cmake errors > lldb-x86_64-ubuntu-14.04-android cmake errors > lldb-x86_64-ubuntu-14.04-buildserver green > lldb-x86_64-ubuntu-14.04-cmake test failures > Thanks for your feedback. As one of the people who encouraged users to report failures they see locally, I would like to point out I wasn't really aware of the existence of many of these bots. I'm aware there's a subset of people watching the MacOS bots, which are now in a decent state (as part of their day job). (I personally never heard of the darwin-13.4 bot but if overlaps with what the lldb greendragon bots are testing, it could be as well dismissed, i.e. http://lab.llvm.org:8080/green/view/LLDB/) I will personally watch these bots more closely, I cc:ed some of the people involved to see if we can make the situation better. Have you considered debugging some of the issues you're seeing locally? I'm pretty sure some help would be appreciated. -- Davide ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 40295] New: TestLibCxxFunction is flaky on Linux (Ubuntu)
https://bugs.llvm.org/show_bug.cgi?id=40295 Bug ID: 40295 Summary: TestLibCxxFunction is flaky on Linux (Ubuntu) Product: lldb Version: 7.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: sti...@microsoft.com CC: llvm-b...@lists.llvm.org TestLibCxxFunction will sometimes fail on Linux. The test usually fails when the test suite is invoked via: make check-all or make check-lldb and it usually passes if the test is run directly through dotest.py. The failure is (usually) in the dwarf version of the test and the error is: Segmentation fault. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLDB bot health
Thanks Davide, I think several of these bots have not been maintained for a while. One thing we could do is try to ping the owners and see if it's possible to update the bots or if they're no longer useful, then remove them. Thanks, -Stella -Original Message- From: Davide Italiano Sent: Friday, January 11, 2019 12:54 PM To: Robinson, Paul ; Pavel Labath ; Zachary Turner ; Stella Stamenova Cc: LLDB Subject: Re: [lldb-dev] LLDB bot health On Fri, Jan 11, 2019 at 9:20 AM via lldb-dev wrote: > > Inspired by people recently asking about or filing bugs for test fails > that happen in their own environments, I thought I might do the same. > "But wait," I thought, "maybe some bots are already finding these." > > Which led me to discover: > > lldb-amd64-ninja-netbsd8 green > lldb-windows7-androidtest failures > lldb-x64-windows-ninja test failures > lldb-x86-windows-msvc2015out of disk space > lldb-x86_64-darwin-13.4 cmake errors > lldb-x86_64-ubuntu-14.04-android cmake errors > lldb-x86_64-ubuntu-14.04-buildserver green > lldb-x86_64-ubuntu-14.04-cmake test failures > Thanks for your feedback. As one of the people who encouraged users to report failures they see locally, I would like to point out I wasn't really aware of the existence of many of these bots. I'm aware there's a subset of people watching the MacOS bots, which are now in a decent state (as part of their day job). (I personally never heard of the darwin-13.4 bot but if overlaps with what the lldb greendragon bots are testing, it could be as well dismissed, i.e. https://nam06.safelinks.protection.outlook.com/?url=http%3A%2F%2Flab.llvm.org%3A8080%2Fgreen%2Fview%2FLLDB%2F&data=02%7C01%7CSTILIS%40microsoft.com%7C1047afc43f0b457102c908d67806f31f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636828368585475545&sdata=5UGO69QDiMvM2reR9FP5CxoJeGHQswClNbBdfYFpT4I%3D&reserved=0) I will personally watch these bots more closely, I cc:ed some of the people involved to see if we can make the situation better. Have you considered debugging some of the issues you're seeing locally? I'm pretty sure some help would be appreciated. -- Davide ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLDB bot health
On Fri, Jan 11, 2019 at 3:07 PM Stella Stamenova wrote: > > Thanks Davide, > > I think several of these bots have not been maintained for a while. One thing > we could do is try to ping the owners and see if it's possible to update the > bots or if they're no longer useful, then remove them. > I agree. I don't know who owns these bots, is there an easy way to find? (or just cc: them to these e-mail). We can then ask Galina to just remove the bots if nobody maintains them. Thanks, -- Davide ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLDB bot health
I own this one: lldb-x86-windows-msvc2015 It can be removed, especially now that Stella's is strictly better than mine was even when it was working. There will probably be an effort on our side to get the Linux bots up and running again "soon", but I don't have an exact timeline right now. On Fri, Jan 11, 2019 at 3:12 PM Davide Italiano wrote: > On Fri, Jan 11, 2019 at 3:07 PM Stella Stamenova > wrote: > > > > Thanks Davide, > > > > I think several of these bots have not been maintained for a while. One > thing we could do is try to ping the owners and see if it's possible to > update the bots or if they're no longer useful, then remove them. > > > > I agree. I don't know who owns these bots, is there an easy way to > find? (or just cc: them to these e-mail). > We can then ask Galina to just remove the bots if nobody maintains them. > > Thanks, > > -- > Davide > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] LLDB bot health
If you look at the bot online, there's usually an admin listed. For example: http://lab.llvm.org:8011/buildslaves I've CC'd the admins of the bots from Paul's list that are failing. Thanks, -Stella -Original Message- From: Davide Italiano Sent: Friday, January 11, 2019 3:12 PM To: Stella Stamenova Cc: Robinson, Paul ; Pavel Labath ; Zachary Turner ; LLDB Subject: Re: [lldb-dev] LLDB bot health On Fri, Jan 11, 2019 at 3:07 PM Stella Stamenova wrote: > > Thanks Davide, > > I think several of these bots have not been maintained for a while. One thing > we could do is try to ping the owners and see if it's possible to update the > bots or if they're no longer useful, then remove them. > I agree. I don't know who owns these bots, is there an easy way to find? (or just cc: them to these e-mail). We can then ask Galina to just remove the bots if nobody maintains them. Thanks, -- Davide ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
