[lldb-dev] Test Failures on Linux

Zachary Turner zturner at google.com
Tue Feb 17 09:31:43 PST 2015


Thanks, good to know. But the bigger issue is that a red bot is a useless
bot. If there are known failures, tests should be XFAILed or disabled until
fixes go in, so that people who commit subsequent additional failures know
they've done so.
On Tue, Feb 17, 2015 at 9:27 AM Vince Harron <vharron at google.com> wrote:

> For review that is.
> On Feb 17, 2015 9:27 AM, wrote:
>
> I uploaded a CL to fix these yesterday.
>  On Feb 17, 2015 9:22 AM, "Pavel Labath" <labath at google.com> wrote:
>
> These are fairly old test failures, they should not be related to the
> recent breakage. I believe we have someone looking into them, but I don't
> know who it is. o:)
>
> On 17 February 2015 at 17:04, Zachary Turner <zturner at google.com> wrote:
>
>> I'm getting these test failures on linux righ tnow.
>>
>> I'm still getting these test failures on Linux:
>>
>> FAIL: LLDB (suite) :: TestDataFormatterAdv.py (Linux
>> zturner-goobuntu.mtv.corp.google.com 3.13.0-45-generic #74-Ubuntu SMP
>> Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64)
>> FAIL: LLDB (suite) :: TestDataFormatterCpp.py (Linux
>> zturner-goobuntu.mtv.corp.google.com 3.13.0-45-generic #74-Ubuntu SMP
>> Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64)
>> FAIL: LLDB (suite) :: TestDataFormatterSmartArray.py (Linux
>> zturner-goobuntu.mtv.corp.google.com 3.13.0-45-generic #74-Ubuntu SMP
>> Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64)
>>
>>
>> Are these new test failures?  Are they known about?  If they're known,
>> can we XFAIL them to get a clean run?  If they're new, does anyone know
>> which CL caused it?   A discussion on IRC this morning involved someone who
>> committed something last week which caused 20 new failures.  But he never
>> got an email about it so he didn't know to fix it, because the bots are
>> always red.  This is why we need to immediately revert things that break
>> the build, so that anyone who breaks the build knows about it and can fix
>> it, and not let it linger to the point that it's impossible to revert.
>>
>>
>>
>> _______________________________________________
>> lldb-dev mailing list
>> lldb-dev at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>>
>>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20150217/f2ef55fc/attachment.html>


More information about the lldb-dev mailing list