[lldb-dev] [Bug 25847] New: "f s <#>" fails as short form for "frame select <#>"

https://llvm.org/bugs/show_bug.cgi?id=25847 Bug ID: 25847 Summary: "f s <#>" fails as short form for "frame select <#>" Product: lldb Version: unspecified Hardware: PC OS: FreeBSD Status: NEW Severity: nor

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] Problem with dotest_channels.py

Yeah I'll have a look at what it's doing. I wouldn't expect a return to crash there, just not receive the data. I'm guessing other parts of asyncore code might be doing invalid things with the socket at that point. We do need to be able to handle this case, though, on timeouts that kill the send

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] [3.8 Release] Schedule and call for testers

I can do SLES. I also have an arm7l ubuntu 15.x machine if no one else is already covering that target. On Mon, Dec 14, 2015 at 3:26 PM, Nikola Smiljanic wrote: > I'll do Fedora and openSUSE. > > On Mon, Dec 14, 2015 at 9:08 PM, Daniel Sanders > wrote: > >> Sounds good to me. I'll do the usual

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] Problem with dotest_channels.py

I wonder if you need a flush somewhere before you invoke the cleanup func? Would that do it? It looks like the sending side of the connection is closing before the receiving side has received all its data. On Tue, Dec 15, 2015 at 3:49 PM Adrian McCarthy wrote: > With Todd's change, I was gettin

[lldb-dev] [Bug 25844] New: test rerun logic is hanging on android cross compiler buildbot

https://llvm.org/bugs/show_bug.cgi?id=25844 Bug ID: 25844 Summary: test rerun logic is hanging on android cross compiler buildbot Product: lldb Version: unspecified Hardware: PC OS: All Status: N

[lldb-dev] [Bug 25844] test rerun logic is hanging on android cross compiler buildbot

https://llvm.org/bugs/show_bug.cgi?id=25844 Todd Fiala changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|lldb-dev@lists.llvm.or

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] Problem with dotest_channels.py

With Todd's change, I was getting a Ninja crash. Zach and I replaced the returns Todd added with raises, in order to propagate the exception up the stack, and that avoids the Ninja crash, so I'll check that in in a moment. In the mean time, here's the error message we got out of it. 155 out of 4

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

[lldb-dev] expected timeouts and reruns

Hi all, If you happen to use --rerun-all-issues to turn on test rerunning (via single worker thread) for any failed issue, one thing to be aware of is that expected timeouts that do time out will not be rerun. They are not eligible for rerun (at least as of r255641) since they wouldn't cause the