[Lldb-commits] [PATCH] Skip lldb-mi tests on FreeBSD for now

[Vince Harron]

Can you please send me your build & run script for Linux?

When I checkout and build that revision on Linux, I get the following
failures.

OK (skipped=2)
Ran 356 tests.
Failing Tests (6)
TIMEOUT: LLDB (suite) :: TestAttachDenied.py (Linux tifa.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) :: TestMiExec.py (Linux tifa.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) :: TestMiInterpreterExec.py (Linux
tifa.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) :: TestMiSignal.py (Linux tifa.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) :: TestMiStack.py (Linux tifa.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) :: TestProcessIO.py (Linux tifa.mtv.corp.google.com
3.13.0-45-generic #74-Ubuntu SMP Tue Jan 13 19:36:28 UTC 2015 x86_64 x86_64)
ninja: build stopped: subcommand failed.

You can reproduce using the following steps:

+ ROOT_DIR=/usr/local/google/home/vharron/bisect/tmp
+ rm -rf /usr/local/google/home/vharron/bisect/tmp
+ mkdir -p /usr/local/google/home/vharron/bisect/tmp
+ cd /usr/local/google/home/vharron/bisect/tmp
+ svn co https://llvm.org/svn/llvm-project/lldb/trunk lldb -q -r 231072
+ svn co https://llvm.org/svn/llvm-project/llvm/trunk llvm -q -r 231072
+ svn co https://llvm.org/svn/llvm-project/cfe/trunk clang -q -r 231072
+ wait
+ ln -s ../../clang llvm/tools/clang
+ ln -s ../../lldb llvm/tools/lldb
+ mkdir /usr/local/google/home/vharron/bisect/tmp/build
+ cd /usr/local/google/home/vharron/bisect/tmp/build
+ cmake -GNinja -DCMAKE_C_COMPILER=clang-3.5
-DCMAKE_CXX_COMPILER=clang++-3.5 -DCMAKE_BUILD_TYPE=Debug ../llvm
+ ninja
+ ninja check-lldb



On Fri, Mar 6, 2015 at 11:49 AM, Ilia K <ki.stfu at gmail.com> wrote:

> Hello Vince,
>
> I had tested it on Linux ~5 days ago and all tests passed after r231072.
>
> Thanks,
> Ilia
>
> On Fri, Mar 6, 2015 at 8:32 PM, Vince Harron <vharron at google.com> wrote:
>
>> Hi Abid,
>>
>> Any news on the TestMi failures on Linux?
>>
>>
>> http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/568
>>
>> Thanks,
>>
>> Vince
>>
>>
>>
>>
>> On Tue, Feb 24, 2015 at 2:13 AM, Abid, Hafiz <Hafiz_Abid at mentor.com>
>> wrote:
>>
>>>  HI Vince,
>>>
>>> I will look at these Linux failures.
>>>
>>>  Regards,
>>>
>>> Abid
>>>
>>>
>>>
>>> *From:* lldb-commits-bounces at cs.uiuc.edu [mailto:
>>> lldb-commits-bounces at cs.uiuc.edu] *On Behalf Of *Vince Harron
>>> *Sent:* 24 February 2015 05:35
>>> *To:* dawn at burble.org
>>> *Cc:* reviews+D7727+public+2cad6825c670cc07 at reviews.llvm.org;
>>> lldb-commits
>>> *Subject:* Re: [Lldb-commits] [PATCH] Skip lldb-mi tests on FreeBSD for
>>> now
>>>
>>>
>>>
>>> Hi Dawn,
>>>
>>>
>>>
>>> Thanks for your reply.  I'm getting a bunch of failures on Linux/OSX
>>> platforms when running the lldb-mi tests.  All three Linux buildbots are
>>> showing failures.
>>>
>>>
>>>
>>> http://lab.llvm.org:8011/builders/lldb-x86_64-debian-clang/builds/3701
>>>
>>> http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.10/builds/923
>>>
>>> (scroll to the bottom)
>>>
>>>
>>> http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/216/steps/test%20lldb/logs/stdio
>>>
>>>
>>>
>>> I'm really excited about getting the lldb-mi tests passing, we need more
>>> test coverage.
>>>
>>>
>>>
>>> Please fix these failures ASAP or skip/xfail if it's going to take more
>>> than a few hours.  I'd appreciate if you kept an eye on the buildbots as
>>> well.
>>>
>>>
>>>
>>> Can you send me a script I can use to build and run tests on Linux
>>> and/or OSX?
>>>
>>>
>>>
>>> > I've had tests hang when I've run them on my Mac, but again, not
>>> the lldb-mi tests.
>>>
>>>
>>>
>>> $ brew install coreutils
>>>
>>>
>>>
>>> will give you gtimeout.  If it's in your path, dosep will pick it up and
>>> kill any test that outlives a default timeout.  Very, very useful for
>>> buildservers.
>>>
>>>
>>>
>>> Sincerely,
>>>
>>>
>>>
>>> Vince
>>>
>>>
>>>
>>>
>>>
>>> On Mon, Feb 23, 2015 at 10:00 PM, <dawn at burble.org> wrote:
>>>
>>> On Thu, Feb 19, 2015 at 12:54:56PM -0800, Vince Harron wrote:
>>>
>>> > How stable are your tests on OSX?  If you run them 100 times, what are
>>> the
>>> > results?
>>>
>>> They are very stable and run constantly throughout the day via Jenkins
>>> builds.  We have had issues, but not from the lldb-mi tests.  For
>>> instance, we have had to skip the gdbserver tests because they were
>>> leaving zombies around, presumably due to problems with the permissions
>>> of our Jenkins test user (anyone else run into that?).
>>>
>>> I've had tests hang when I've run them on my Mac, but again, not the
>>> lldb-mi tests.  The hangs seemed to occur in certain tests if I had
>>> another build/test running at the same time.
>>>
>>>
>>>
>>>
>>>
>>> --
>>>
>>>
>>>
>>> Vince Harron |
>>>
>>>  Technical Lead Manager |
>>>
>>>  vharron at google.com |
>>>
>>>  858-442-0868
>>>
>>>
>>>
>>
>>
>>
>> --
>>
>> Vince Harron | Technical Lead Manager | vharron at google.com | 858-442-0868
>>
>> _______________________________________________
>> lldb-commits mailing list
>> lldb-commits at cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
>>
>>
>


-- 

Vince Harron | Technical Lead Manager | vharron at google.com | 858-442-0868
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20150306/5d3cdafb/attachment.html>