[lldb-dev] [Bug 35228] New: TestConcurrentTwoWatchpointsOneSignal flaky on linux arm64

2017-11-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=35228 Bug ID: 35228 Summary: TestConcurrentTwoWatchpointsOneSignal flaky on linux arm64 Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW

Re: [lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot

2017-11-07 Thread Zachary Turner via lldb-dev
Yea, adding a FORCE for a day or two and then removing the FORCE several days later is a good way to handle this kind of thing. On Tue, Nov 7, 2017 at 10:42 AM Reid Kleckner via lldb-dev < lldb-dev@lists.llvm.org> wrote: > In general, please try to structure changes so that CMake cache clobbers >

Re: [lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot

2017-11-07 Thread Reid Kleckner via lldb-dev
In general, please try to structure changes so that CMake cache clobbers aren't necessary. If you introduce changes that require clobbers by accident, consider adding some temporary CMake logic to help buildbots recover on their own. Some temporary CMake hacks can save a lot of time across all the

Re: [lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot

2017-11-07 Thread Jim Ingham via lldb-dev
Good news. I got somebody to kick the llvm.org bots, so sounds like this should solve the problem. Jim > On Nov 7, 2017, at 10:36 AM, Ted Woodward wrote: > > We had the same problem internally on our bots. A clean build blew away the > cmake caches and fixed the problem. > > Ted > -- > Qu

Re: [lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot

2017-11-07 Thread Ted Woodward via lldb-dev
We had the same problem internally on our bots. A clean build blew away the cmake caches and fixed the problem. Ted -- Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project From: lldb-dev [mailto

Re: [lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot

2017-11-07 Thread Jim Ingham via lldb-dev
NP, I'll find somebody who can initiate a clean rebuild. Jim > On Nov 7, 2017, at 10:28 AM, Pavel Labath wrote: > > You probably just need to nuke the build folder. > > The reason for that is that before the patch the LLDB_TEST_C_COMPILER > variable was used for a different purpose (and usual

Re: [lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot

2017-11-07 Thread Pavel Labath via lldb-dev
You probably just need to nuke the build folder. The reason for that is that before the patch the LLDB_TEST_C_COMPILER variable was used for a different purpose (and usually empty), where as now it's set by default to the in-tree clang. However, cmake will not overwrite the cached value by design.

Re: [lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot

2017-11-07 Thread Don Hinton via lldb-dev
I hit the same problem last week. I ended up blowing away my build directory, and the problem went away. Probably a cache issue, but I was unable to reproduce... On Tue, Nov 7, 2017 at 10:21 AM, Jim Ingham via lldb-dev < lldb-dev@lists.llvm.org> wrote: > The lldb_cmake GreenDragon bot is now fa

[lldb-dev] Bot failure with new "in tree compiler" changes (r316728) in llvm.org bot

2017-11-07 Thread Jim Ingham via lldb-dev
The lldb_cmake GreenDragon bot is now failing, e.g.: http://lab.llvm.org:8080/green/view/LLDB/job/lldb_cmake/1703/consoleFull#589016626e9a0fee5-ebcc-4238-a641-c5aa112c323e This looks related to Pavel's change: > r316728 | labath | 2017-10-26 19:24:04 -0700 (Thu, 26 Oct 2017) | 18 lines > > Defa

[lldb-dev] [Bug 35224] New: Watchpoint in atomic sequences are not supported on arm

2017-11-07 Thread via lldb-dev
https://bugs.llvm.org/show_bug.cgi?id=35224 Bug ID: 35224 Summary: Watchpoint in atomic sequences are not supported on arm Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW