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 <ztur...@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@cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev > >
_______________________________________________ lldb-dev mailing list lldb-dev@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev