Re: [lldb-dev] test rerun phase is in

Hmm okay I've now seen this on internal CI at least once when a rerun occurred. I'm going to switch the rerun to work with the multithreaded test runner with a single worker. Right now it is using the serial test runner, which I don't think gets nearly as much testing as the others and might be th

Re: [lldb-dev] test rerun phase is in

I see that build #4314 no longer hanged on aarch64. (It failed, but for what looks like legitimate reasons). I'll make the change for arm as well. -Todd On Tue, Dec 15, 2015 at 5:14 PM, Todd Fiala wrote: > Arg okay. > > I restarted the aarch64 builder so that it will pick up my suppression >

Re: [lldb-dev] test rerun phase is in

Arg okay. I restarted the aarch64 builder so that it will pick up my suppression there. I'll adjust it to suppress for arm as well, I'll have to hit that in about an hour or so but I will do it tonight. -Todd On Tue, Dec 15, 2015 at 4:00 PM, Ying Chen wrote: > It also happened for -A arm. > >

Re: [lldb-dev] test rerun phase is in

It also happened for -A arm. http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-android/builds/4307/steps/test7/logs/stdio On Tue, Dec 15, 2015 at 3:46 PM, Todd Fiala wrote: > Hey Ying, > > I'm going to check in something that stops the rerun logic when both (1) > -A aarch64 is specified

Re: [lldb-dev] test rerun phase is in

On Tue, Dec 15, 2015 at 3:36 PM, Todd Fiala wrote: > #4310 failed for some other reason. > Sorry for the confusion, the builds on android builders should be triggered by android buildserver , since that's where lldb-server w

Re: [lldb-dev] test rerun phase is in

Hey Ying, I'm going to check in something that stops the rerun logic when both (1) -A aarch64 is specified and (2) --rerun-all-issues is not specified. That'll give me some time to drill into what's getting stuck on the android buildbot. -Todd On Tue, Dec 15, 2015 at 3:36 PM, Todd Fiala wrote:

Re: [lldb-dev] test rerun phase is in

#4310 failed for some other reason. #4311 looks like it might be stuck in the test3 phase but it is showing less output than it had before (maybe because it hasn't timed out yet). I'm usually running with --rerun-all-issues, but I can force similar failures to what this bot is seeing when I crank

Re: [lldb-dev] test rerun phase is in

Build >= #4310 is what I'll be watching. On Tue, Dec 15, 2015 at 2:30 PM, Todd Fiala wrote: > Okay cool. Will do. > > On Tue, Dec 15, 2015 at 2:22 PM, Ying Chen wrote: > >> Sure. Please go ahead to do that. >> BTW, the pending builds should be merged into one build once current >> build is do

Re: [lldb-dev] test rerun phase is in

Okay cool. Will do. On Tue, Dec 15, 2015 at 2:22 PM, Ying Chen wrote: > Sure. Please go ahead to do that. > BTW, the pending builds should be merged into one build once current build > is done. > > On Tue, Dec 15, 2015 at 2:12 PM, Todd Fiala wrote: > >> Hey Ying, >> >> Do you mind if we clear

Re: [lldb-dev] test rerun phase is in

Sure. Please go ahead to do that. BTW, the pending builds should be merged into one build once current build is done. On Tue, Dec 15, 2015 at 2:12 PM, Todd Fiala wrote: > Hey Ying, > > Do you mind if we clear the android builder queue to get a build with > r255676 in it? There are what looks li

Re: [lldb-dev] test rerun phase is in

Hey Ying, Do you mind if we clear the android builder queue to get a build with r255676 in it? There are what looks like at least 3 or 4 builds between now and then, and with timeouts it may take several hours. -Todd On Tue, Dec 15, 2015 at 1:50 PM, Ying Chen wrote: > Yes, it happens every ti

Re: [lldb-dev] test rerun phase is in

Yes, it happens every time for android builder. On Tue, Dec 15, 2015 at 1:45 PM, Todd Fiala wrote: > Hmm, yeah it looks like it did the rerun and then after finishing the > rerun, it's just hanging. > > Let's have a look right after r255676 goes through this builder. I hit a > hang in the curse

Re: [lldb-dev] test rerun phase is in

Hmm, yeah it looks like it did the rerun and then after finishing the rerun, it's just hanging. Let's have a look right after r255676 goes through this builder. I hit a hang in the curses output display due to the recursive taking of a lock on a lock that was not recursive-enabled. While I would

Re: [lldb-dev] test rerun phase is in

Yep, I'll have a look! On Tue, Dec 15, 2015 at 12:43 PM, Ying Chen wrote: > Hi Todd, > > It is noticed on lldb android builders that the test_runner didn't exit > after rerun, which caused buildbot timeout since the process was hanging > for over 20 minutes. > Could you please take a look if tha

Re: [lldb-dev] test rerun phase is in

Hi Todd, It is noticed on lldb android builders that the test_runner didn't exit after rerun, which caused buildbot timeout since the process was hanging for over 20 minutes. Could you please take a look if that's related to your change? Please see the following builds. http://lab.llvm.org:8011/b

Re: [lldb-dev] test rerun phase is in

And, btw, this shows the rerun logic working (via the --rerun-all-issues flag): time test/dotest.py --executable `pwd`/build/Debug/lldb --threads 24 --rerun-all-issues Testing: 416 test suites, 24 threads 377 out of 416 test suites processed - TestSBTypeTypeClass.py Session logs for test failures

Re: [lldb-dev] test rerun phase is in

And that fixed the rest as well. Thanks, Siva! -Todd On Mon, Dec 14, 2015 at 4:44 PM, Todd Fiala wrote: > Heh you were skinning the same cat :-) > > That fixed the one I was just looking at, running the others now. > > On Mon, Dec 14, 2015 at 4:42 PM, Todd Fiala wrote: > >> Yep, will try now.

Re: [lldb-dev] test rerun phase is in

Heh you were skinning the same cat :-) That fixed the one I was just looking at, running the others now. On Mon, Dec 14, 2015 at 4:42 PM, Todd Fiala wrote: > Yep, will try now... (I was just looking at the condition testing logic > since it looks like something isn't quite right there). > > On

Re: [lldb-dev] test rerun phase is in

Yep, will try now... (I was just looking at the condition testing logic since it looks like something isn't quite right there). On Mon, Dec 14, 2015 at 4:39 PM, Siva Chandra wrote: > Can you try again after taking my change at r255584? > > On Mon, Dec 14, 2015 at 4:31 PM, Todd Fiala via lldb-de

Re: [lldb-dev] test rerun phase is in

Can you try again after taking my change at r255584? On Mon, Dec 14, 2015 at 4:31 PM, Todd Fiala via lldb-dev wrote: > I'm having some of these blow up. > > In the case of test/lang/c/typedef/Testtypedef.py, it looks like some of the > @expected decorators were changed a bit, and perhaps they are

Re: [lldb-dev] test rerun phase is in

The full set that are blowing up are: = Issue Details = FAIL: test_expr_stripped_dwarf (lang/objc/hidden-ivars/TestHiddenIvars.py) FAIL: test_frame_variable_stripped_dwarf (lang/objc/hidden-ivars/TestHiddenIvars.py) FAIL: test_typedef_dsym (lang/c/typedef/Testtypedef.py) FA

Re: [lldb-dev] test rerun phase is in

I'm having some of these blow up. In the case of test/lang/c/typedef/Testtypedef.py, it looks like some of the @expected decorators were changed a bit, and perhaps they are not pound for pound the same. For example, this test used to really be marked XFAIL (via an expectedFailureClang directive),

Re: [lldb-dev] test rerun phase is in

I've checked in r255567 which fixes a problem pointed out by Siva. It doesn't sound related to in 255542, but looking at those logs I can't really tell how my CL would be related. If r255567 doesn't fix the bots, would someone mind helping me briefly? r255542 seems pretty straightforward, so I d

Re: [lldb-dev] test rerun phase is in

Ah yes I see. Thanks, Ying (and Siva! Saw your comments too). On Mon, Dec 14, 2015 at 2:34 PM, Ying Chen wrote: > Seems this is the first build that fails, and it only has one CL 255542 > . > > http://lab.llvm.org:8011/builders/lld

Re: [lldb-dev] test rerun phase is in

Seems this is the first build that fails, and it only has one CL 255542 . http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-cmake/builds/9446 I believe Zachary is looking at that problem. On Mon, Dec 14, 2015 at 2:18 PM, Todd

Re: [lldb-dev] test rerun phase is in

I am seeing several failures on the Ubuntu 14.04 testbot, but unfortunately there are a number of changes that went in at the same time on that build. The failures I'm seeing are not appearing at all related to the test running infrastructure. Anybody with a fast Linux system able to take a look t

[lldb-dev] test rerun phase is in

Hi all, I just put in the single-worker, low-load, follow-up test run pass in r255543. Most of the work for it went in late last week, this just mostly flips it on. The feature works like this: * First test phase works as before: run all tests using whatever level of concurrency is normally use