<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 4:41 PM, Todd Fiala <span dir="ltr"><<a href="mailto:todd.fiala@gmail.com" target="_blank">todd.fiala@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Chaoren,<div><br></div><div>Right you are, I am using a VMWare VM. Usually when I have issues with VMs, it is because I'm not using VMWare, so this is a change!</div><div><br></div></div></blockquote><div><br></div><div>And I am happy to report I get *no* errors when building with clang-3.6 + ld.gold + Debug on real iron.</div><div><br></div><div>Thanks for the help, everyone!</div><div><br></div><div>-Todd</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>Do you have a reference to a VMWare bug on this? That would be great to follow up with them on.</div><div><br></div><div>In the absence of that, I wonder if we can detect that is the runtime environment and perhaps skip that test on VMWare VMs. I'm pretty sure we can detect that we're running in a VM if (at least) the guest tools are installed. I'll look into that.</div><div><br></div><div>-Todd</div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 4:26 PM, Chaoren Lin <span dir="ltr"><<a href="mailto:chaorenl@google.com" target="_blank">chaorenl@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Sorry, "kernel" bug is probably the wrong word. It's a problem specific to WMware.</div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 4:25 PM, Chaoren Lin <span dir="ltr"><<a href="mailto:chaorenl@google.com" target="_blank">chaorenl@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Are you running VMware by any chance? <span style="color:rgb(80,0,80);font-size:12.8000001907349px">TestStepOverWatchpoint fails on VMware because of a kernel bug.</span></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 4:17 PM, Todd Fiala <span dir="ltr"><<a href="mailto:todd.fiala@gmail.com" target="_blank">todd.fiala@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">One more data point:<div><br></div><div>Building/testing on Ubuntu 14.04.3 built with clang-3.6 and the ld.gold linker yielded the following test results, bringing me down to a single failure (and was 1.6x faster than a Debug build with gcc-4.9 and ld.bfd, 12 GB RAM and 6 cores allocated):</div><div><br></div><div><div>Failing Tests (1)</div><span><div>FAIL: LLDB (suite) :: TestStepOverWatchpoint.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div><br></div></span><div>Unexpected Successes (12)</div><span><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestBatchMode.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div></span><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestConstVariables.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><span><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestEvents.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestExitDuringStep.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestFdLeak.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestInferiorAssert.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestMiGdbSetShow.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestMiInterpreterExec.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestMiSyntax.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestRaise.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestStubSetSID.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestWatchedVarHitWhenInScope.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div></span></div><div><br></div><div><br></div><div>I'm not yet sure if that's stable, but it's what I'm seeing on my VM.</div><div><br></div><div>-Todd</div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 1:56 PM, Todd Fiala <span dir="ltr"><<a href="mailto:todd.fiala@gmail.com" target="_blank">todd.fiala@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">So specifying CC=/usr/bin/gcc CXX=/usr/bin/g++ cmake -GNinja ...<div><br></div><div>did the trick for getting rid of the libc++ issues. I think I may try to see if we can get those tests to make a run-time check to see if the inferior is linked against libc++, and if not, to skip it. We can have lldb do it by looking at the image list. Sound reasonable? That seems more fool-proof than guessing based on the compiler.</div><div><br></div><div>An alternative I considered and probably also might be valid to do anyway for cases where we look at the compiler binary is to fully resolve symbolic links before making decisions based on the binary.</div><div><br></div><div>Thoughts?</div><div><br></div><div>Separately, with the tests correctly seeing gcc now, I am down to the following errors:</div><div><br></div><div><div>Ran 394 test suites (5 failed) (1.269036%)</div><div>Ran 451 test cases (5 failed) (1.108647%)</div><div>Failing Tests (5)</div><div>FAIL: LLDB (suite) :: TestExitDuringStep.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>FAIL: LLDB (suite) :: TestNumThreads.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><span><div>FAIL: LLDB (suite) :: TestRegisterVariables.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div></span><span><div>FAIL: LLDB (suite) :: TestStepOverWatchpoint.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div></span><div>FAIL: LLDB (suite) :: TestThreadExit.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div><br></div><div>Unexpected Successes (10)</div><span><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestBatchMode.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestEvents.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div></span><span><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestFdLeak.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestInferiorAssert.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestMiGdbSetShow.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestMiInterpreterExec.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestMiSyntax.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestRaise.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestStubSetSID.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div><div>UNEXPECTED SUCCESS: LLDB (suite) :: TestWatchedVarHitWhenInScope.py (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)</div></span></div><div><br></div><div><br></div><div>Some of those failures look like old friends that were failing a year ago. Can anybody tell me anything about those failures on Linux? Are they being looked at? Any hunches at to what is wrong?</div><div><br></div><div>Thanks!</div><div><br></div><div>-Todd</div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 10:04 AM, Todd Fiala <span dir="ltr"><<a href="mailto:todd.fiala@gmail.com" target="_blank">todd.fiala@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Okay.<div><br></div><div>So the culprit then is that I'm using:</div><div>cmake -GNinja ../llvm</div><div><br></div><div>with one extra flag for build type. And cmake is then just choosing /usr/bin/cc.</div><div><br></div><div>We could improve this by having the compiler symbolic links fully resolved:</div><div>/usr/bin/cc -> /etc/alternatives/cc -> /usr/bin/gcc, which would have then caught that it doesn't support libc++.</div><div><br></div><div>Couldn't we use gcc with libc++? (i.e. is it sufficient to assume we don't have libc++ if we're using gcc?) I have never tried that combo but I don't know that it is impossible. (After all, I just added libc++-dev to the system, which presumably I can link against).</div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 9:48 AM, Tamas Berghammer <span dir="ltr"><<a href="mailto:tberghammer@google.com" target="_blank">tberghammer@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">In theory the test should be skipped when you are using gcc (cc is an alias for it) but we detect the type of the compiler based on the executable name and in case of cc we don't recognize that it is a gcc, so we don't skip the test.<div><div><div><div><br><div class="gmail_quote"><div dir="ltr">On Tue, Aug 25, 2015 at 5:45 PM Chaoren Lin via lldb-dev <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">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">You're using CC="/usr/bin/cc". It needs to be clang for USE_LIBCPP to do anything. :/</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 9:20 AM, Todd Fiala <span dir="ltr"><<a href="mailto:todd.fiala@gmail.com" target="_blank">todd.fiala@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Here are a couple of the failures that came up (the log output from the full dosep.py run).<div><br></div><div>Let me know if that is not sufficient!</div></div><div class="gmail_extra"><div><div><br><div class="gmail_quote">On Tue, Aug 25, 2015 at 9:14 AM, Pavel Labath <span dir="ltr"><<a href="mailto:labath@google.com" target="_blank">labath@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">There's no need to do anything fancy (yet :) ). For initial diagnosis<br>
the output of `./dotest.py $your_usual_options -p SomeLibcxxTest.py<br>
-t` should suffice.<br>
<span><font color="#888888"><br>
pl<br>
</font></span><div><div><br>
On 25 August 2015 at 16:45, Todd Fiala <<a href="mailto:todd.fiala@gmail.com" target="_blank">todd.fiala@gmail.com</a>> wrote:<br>
> Thanks, Pavel! I'll dig that up and get back.<br>
><br>
> On Tue, Aug 25, 2015 at 8:30 AM, Pavel Labath <<a href="mailto:labath@google.com" target="_blank">labath@google.com</a>> wrote:<br>
>><br>
>> There is no separate option, it should just work. :)<br>
>><br>
>> I'm betting you are still missing some package there (we should<br>
>> document the prerequisites better). Could you send the error message<br>
>> you are getting so we can have a look.<br>
>><br>
>> cheers,<br>
>> pl<br>
>><br>
>><br>
>> On 25 August 2015 at 16:20, Todd Fiala via lldb-dev<br>
>> <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br>
>> ><br>
>> ><br>
>> > On Mon, Aug 24, 2015 at 4:11 PM, Todd Fiala <<a href="mailto:todd.fiala@gmail.com" target="_blank">todd.fiala@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >><br>
>> >><br>
>> >> On Mon, Aug 24, 2015 at 4:01 PM, Chaoren Lin <<a href="mailto:chaorenl@google.com" target="_blank">chaorenl@google.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> The TestDataFormatterLibcc* tests require libc++-dev:<br>
>> >>><br>
>> >>> $ sudo apt-get install libc++-dev<br>
>> >>><br>
>> >><br>
>> >> Ah okay, so we are working with libc++ on Ubuntu, that's good to hear.<br>
>> >> Pre-14.04 I gave up on it.<br>
>> >><br>
>> >> Will cmake automatically choose libc++ if it is present? Or do I need<br>
>> >> to<br>
>> >> pass something to cmake to use libc++?<br>
>> ><br>
>> ><br>
>> > Hmm it appears I need to do more than just install libc++-dev. I did a<br>
>> > clean build with that installed, then ran the tests, and I still have<br>
>> > the<br>
>> > Libcxc/Libcxx tests failing. Is there some flag expected, either to<br>
>> > pass<br>
>> > along for the compile options to dotest.py to override/specify which c++<br>
>> > lib<br>
>> > it is using?<br>
>> ><br>
>> >><br>
>> >><br>
>> >> Thanks, Chaoren!<br>
>> >><br>
>> >> -Todd<br>
>> >><br>
>> >>><br>
>> >>> On Mon, Aug 24, 2015 at 3:42 PM, Todd Fiala via lldb-dev<br>
>> >>> <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br>
>> >>>><br>
>> >>>><br>
>> >>>> On Mon, Aug 24, 2015 at 3:39 PM, Zachary Turner <<a href="mailto:zturner@google.com" target="_blank">zturner@google.com</a>><br>
>> >>>> wrote:<br>
>> >>>>><br>
>> >>>>> Can't comment on the failures for Linux, but I don't think we have a<br>
>> >>>>> good handle on the unexpected successes. I only added that<br>
>> >>>>> information to<br>
>> >>>>> the output about a week ago, before that unexpected successes were<br>
>> >>>>> actually<br>
>> >>>>> going unnoticed.<br>
>> >>>><br>
>> >>>><br>
>> >>>> Okay, thanks Zachary. A while back we had some flapping tests that<br>
>> >>>> would oscillate between unexpected success and failure on Linux.<br>
>> >>>> Some of<br>
>> >>>> those might still be in that state but maybe (!) are fixed.<br>
>> >>>><br>
>> >>>> Anyone on the Linux end who happens to know if the fails in<br>
>> >>>> particular<br>
>> >>>> look normal, that'd be good to know.<br>
>> >>>><br>
>> >>>> Thanks!<br>
>> >>>><br>
>> >>>>><br>
>> >>>>><br>
>> >>>>> It's likely that someone could just go in there and remove the XFAIL<br>
>> >>>>> from those tests.<br>
>> >>>>><br>
>> >>>>> On Mon, Aug 24, 2015 at 3:37 PM Todd Fiala via lldb-dev<br>
>> >>>>> <<a href="mailto:lldb-dev@lists.llvm.org" target="_blank">lldb-dev@lists.llvm.org</a>> wrote:<br>
>> >>>>>><br>
>> >>>>>> Hi all,<br>
>> >>>>>><br>
>> >>>>>> I'm just trying to get a handle on current lldb test failures<br>
>> >>>>>> across<br>
>> >>>>>> different platforms.<br>
>> >>>>>><br>
>> >>>>>> On Linux on non-virtualized hardware, I currently see the failures<br>
>> >>>>>> below on Ubuntu 14.04.2 using a setup like this:<br>
>> >>>>>> * stock linker (ld.bfd),<br>
>> >>>>>> * g++ 4.9.2<br>
>> >>>>>> * cmake<br>
>> >>>>>> * ninja<br>
>> >>>>>> * libstdc++<br>
>> >>>>>><br>
>> >>>>>> ninja check-lldb output:<br>
>> >>>>>><br>
>> >>>>>> Ran 394 test suites (15 failed) (3.807107%)<br>
>> >>>>>> Ran 474 test cases (17 failed) (3.586498%)<br>
>> >>>>>> Failing Tests (15)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestCPPThis.py (Linux rad 3.13.0-57-generic<br>
>> >>>>>> #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibccIterator.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibccMap.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibccMultiMap.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibcxxMultiSet.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibcxxSet.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibcxxString.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterSkipSummary.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterUnordered.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestMiGdbSetShowPrint.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestRegisterVariables.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestStaticVariables.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestStepNoDebug.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic<br>
>> >>>>>> #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestTypedefArray.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic<br>
>> >>>>>> #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestVectorTypesFormatting.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>><br>
>> >>>>>> Unexpected Successes (10)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestBatchMode.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestEvents.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestExitDuringStep.py (Linux<br>
>> >>>>>> rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestFdLeak.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestInferiorAssert.py (Linux<br>
>> >>>>>> rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestMiGdbSetShow.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestMiInterpreterExec.py (Linux<br>
>> >>>>>> rad 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestMiSyntax.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestRaise.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestStubSetSID.py (Linux rad<br>
>> >>>>>> 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> ninja: build stopped: subcommand failed.<br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>> On a similar setup, although bumped up to Ubuntu 14.04.3 and now on<br>
>> >>>>>> a<br>
>> >>>>>> VMWare VM, everything else the same, I see a similar report from<br>
>> >>>>>> 'ninja<br>
>> >>>>>> check-lldb':<br>
>> >>>>>><br>
>> >>>>>> Ran 394 test suites (17 failed) (4.314721%)<br>
>> >>>>>> Ran 474 test cases (19 failed) (4.008439%)<br>
>> >>>>>> Failing Tests (17)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestAttachResume.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestCPPThis.py (Linux lldb 3.19.0-26-generic<br>
>> >>>>>> #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibccIterator.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibccMap.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibccMultiMap.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibcxxMultiSet.py (Linux<br>
>> >>>>>> lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibcxxSet.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterLibcxxString.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterSkipSummary.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestDataFormatterUnordered.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestMiGdbSetShowPrint.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestRegisterVariables.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestStaticVariables.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestStepNoDebug.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic<br>
>> >>>>>> #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC 2015 x86_64 x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestStepOverWatchpoint.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestTypedefArray.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> FAIL: LLDB (suite) :: TestVectorTypesFormatting.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>><br>
>> >>>>>> Unexpected Successes (11)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestBatchMode.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestEvents.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestExitDuringStep.py (Linux<br>
>> >>>>>> lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestFdLeak.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestInferiorAssert.py (Linux<br>
>> >>>>>> lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestMiGdbSetShow.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestMiInterpreterExec.py (Linux<br>
>> >>>>>> lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17<br>
>> >>>>>> UTC 2015<br>
>> >>>>>> x86_64 x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestMiSyntax.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestRaise.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestStubSetSID.py (Linux lldb<br>
>> >>>>>> 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64<br>
>> >>>>>> x86_64)<br>
>> >>>>>> UNEXPECTED SUCCESS: LLDB (suite) :: TestWatchedVarHitWhenInScope.py<br>
>> >>>>>> (Linux lldb 3.19.0-26-generic #28~14.04.1-Ubuntu SMP Wed Aug 12<br>
>> >>>>>> 14:09:17 UTC<br>
>> >>>>>> 2015 x86_64 x86_64)<br>
>> >>>>>> ninja: build stopped: subcommand failed.<br>
>> >>>>>><br>
>> >>>>>><br>
>> >>>>>> Do these more or less match the current state of affairs for Linux<br>
>> >>>>>> tests? If not, are there any suggestions on best practices for<br>
>> >>>>>> upgrades? A<br>
>> >>>>>> while back I had tried things like clang and libc++ but I had<br>
>> >>>>>> arrived at the<br>
>> >>>>>> above setup (albeit typically with the gold linker) simply due to<br>
>> >>>>>> what<br>
>> >>>>>> worked, what was easy to debug and what built fast.<br>
>> >>>>>><br>
>> >>>>>> Thanks for any confirmation on that!<br>
>> >>>>>><br>
>> >>>>>> --<br>
>> >>>>>> -Todd<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>
>> >>>><br>
>> >>>><br>
>> >>>><br>
>> >>>> --<br>
>> >>>> -Todd<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>
>> >>><br>
>> >><br>
>> >><br>
>> >><br>
>> >> --<br>
>> >> -Todd<br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > -Todd<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>
><br>
><br>
><br>
><br>
> --<br>
> -Todd<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div><div dir="ltr">-Todd</div></div>
</font></span></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></div></div></div></div></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div><div dir="ltr">-Todd</div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div><div dir="ltr">-Todd</div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div></div></div><span><font color="#888888">-- <br><div><div dir="ltr">-Todd</div></div>
</font></span></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br><div><div dir="ltr">-Todd</div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">-Todd</div></div>
</div></div>