<div dir="ltr">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.</div><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 7, 2017 at 10:42 AM Reid Kleckner via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org">lldb-dev@lists.llvm.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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 folks that have to discover and debug this problem.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Nov 7, 2017 at 10:28 AM, Pavel Labath via lldb-dev <span dir="ltr"><<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You probably just need to nuke the build folder.<br>
<br>
The reason for that is that before the patch the LLDB_TEST_C_COMPILER<br>
variable was used for a different purpose (and usually empty), where<br>
as now it's set by default to the in-tree clang. However, cmake will<br>
not overwrite the cached value by design. (I could have worked around<br>
that in cmake, but I only noticed that issue after landing the<br>
change.)<br>
<br>
Erasing the build folder should let the new and correct default kick<br>
in. If you run the check-lldb target then it will now use the in-tree<br>
clang instead of the system compiler for using tests.<br>
<br>
sorry about the trouble,<br>
pl<br>
<br>
<br>
<br>
On 7 November 2017 at 18:21, Jim Ingham via lldb-dev<br>
<div class="m_1297228348532420711HOEnZb"><div class="m_1297228348532420711h5"><<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br>
> The lldb_cmake GreenDragon bot is now failing, e.g.:<br>
><br>
> <a href="http://lab.llvm.org:8080/green/view/LLDB/job/lldb_cmake/1703/consoleFull#589016626e9a0fee5-ebcc-4238-a641-c5aa112c323e" rel="noreferrer" target="_blank">http://lab.llvm.org:8080/green/view/LLDB/job/lldb_cmake/1703/consoleFull#589016626e9a0fee5-ebcc-4238-a641-c5aa112c323e</a><br>
><br>
> This looks related to Pavel's change:<br>
><br>
>> r316728 | labath | 2017-10-26 19:24:04 -0700 (Thu, 26 Oct 2017) | 18 lines<br>
>><br>
>> Default to using in-tree clang for building test executables<br>
>><br>
>> Summary:<br>
>> Using the in-tree clang should be the default test configuration as that<br>
>> is the one compiler that we can be sure everyone has (better<br>
>> reproducibility of test results). Also, it should hopefully reduce the<br>
>> impact of pr35040.<br>
>><br>
>> This also reduces the number of settings which control the compiler<br>
>> used. LLDB_TEST_C_COMPILER is used for C files and<br>
>> LLDB_TEST_CXX_COMPILER for C++ files. Both of the settings default to<br>
>> the in-tree clang.<br>
>><br>
>> Reviewers: zturner<br>
>><br>
>> Subscribers: mgorny, davide, lldb-commits<br>
>><br>
>> Differential Revision: <a href="https://reviews.llvm.org/D39215" rel="noreferrer" target="_blank">https://reviews.llvm.org/D39215</a><br>
>><br>
><br>
> The error is:<br>
><br>
> CMake Error at tools/lldb/CMakeLists.txt:78 (message):<br>
><br>
> LLDB test compilers not specified. Tests will not run<br>
><br>
><br>
> Does the bot need to be reconfigured for these changes?<br>
><br>
> Jim<br>
><br>
> _______________________________________________<br>
> lldb-dev mailing list<br>
> <a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a><br>
> <a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br>
_______________________________________________<br>
lldb-dev mailing list<br>
<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br>
</div></div></blockquote></div><br></div>
_______________________________________________<br>
lldb-dev mailing list<br>
<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev" rel="noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev</a><br>
</blockquote></div>