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

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)

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

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

Re: [lldb-dev] Problem with dotest_channels.py

Hey Zachary, I just put in: r255581 which should hopefully: (1) catch the exception you see there, (2) handle it gracefully in the common and to-be-expected case of the test inferior going down hard, and (3) print out an error if anything else unexpected is happening here. Let me know if you

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

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

Re: [lldb-dev] [3.8 Release] Schedule and call for testers

Sounds good to me. I'll do the usual mips packages. > -Original Message- > From: hwennb...@google.com [mailto:hwennb...@google.com] On Behalf > Of Hans Wennborg > Sent: 11 December 2015 23:15 > To: llvm-dev; cfe-dev; lldb-dev@lists.llvm.org; openmp-...@lists.llvm.org > Cc: Dimitry Andric;

[lldb-dev] [Bug 25819] New: TestNamespaceLookup is failing on linux

https://llvm.org/bugs/show_bug.cgi?id=25819 Bug ID: 25819 Summary: TestNamespaceLookup is failing on linux Product: lldb Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal

Re: [lldb-dev] marking new summary output for expected timeouts

Oh yeah, that's fine. I won't take that code out. Hmm at least some of the builds went through this weekend, I made a number of changes Saturday morning (US Pacific time) that I saw go through the Ubuntu 14.04 cmake bot. On Mon, Dec 14, 2015 at 6:29 AM, Pavel Labath wrote:

Re: [lldb-dev] marking new summary output for expected timeouts

Hi, we've had an unrelated breaking change, so the buildbots were red over the weekend. I've fixed it now, and it seems to be turning green. We've also had power outage during the weekend and not all of the buildbots are back up yet, as we need to wait for MTV to wake up. I'd like to give this at

Re: [lldb-dev] BasicResultsFormatter - new test results summary

Hi, thanks a lot for fixing the timeout issue on such a short notice. I didn't think I'd find myself defending them, as I remember being quite upset when they went in, but they have proven useful in stabilising the build bots, and I think it's likely you may need them as well. I'll try to now add

Re: [lldb-dev] BasicResultsFormatter - new test results summary

On 14 December 2015 at 16:19, Todd Fiala wrote: >> We would lose the ability to individually expect "failures" and >> "timeouts", but I don't think that is really necessary, and I think it >> will be worth the extra maintainability we get from the fact of having >> fewer

[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

[lldb-dev] debug info test failures

Hi all, I'm seeing locally on OS X the same build failures that I'm seeing on the ubuntu 14.04 cmake builedbot: ERROR: TestWithLimitDebugInfo.TestWithLimitDebugInfo.test_limit_debug_info_dwarf (lang/cpp/limit-debug-info/TestWithLimitDebugInfo.py) ERROR:

Re: [lldb-dev] debug info test failures

I temporarily skipped these tests on Darwin and Linux here: r255549 I'll file a bug in a moment... On Mon, Dec 14, 2015 at 1:42 PM, Todd Fiala wrote: > Hi all, > > I'm seeing locally on OS X the same build failures that I'm seeing on the > ubuntu 14.04 cmake builedbot: >

[lldb-dev] [Bug 25825] New: TestWithLimitDebugInfo.py causing error

https://llvm.org/bugs/show_bug.cgi?id=25825 Bug ID: 25825 Summary: TestWithLimitDebugInfo.py causing error Product: lldb Version: unspecified Hardware: PC OS: All Status: NEW Severity: normal

Re: [lldb-dev] Problem with dotest_channels.py

If nothing else, maybe we can print out a more useful exception backtrace. What kind of exception, what line, and what was the message? That might help give us a better idea of what's causing it. On Mon, Dec 14, 2015 at 2:03 PM Todd Fiala wrote: > Hi Zachary! > > > > > >

Re: [lldb-dev] debug info test failures

Yea I think r255542 fixes it, or at least it was supposed to. Let me know On Mon, Dec 14, 2015 at 2:04 PM Todd Fiala wrote: > Okay. I appeared to be up to date when hitting it, but we may have > crossed on it. > > I'll take out the skip if I am not hitting it now.

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 > . > >

Re: [lldb-dev] debug info test failures

I believe I already fixed this issue On Mon, Dec 14, 2015 at 1:53 PM Todd Fiala via lldb-dev < lldb-dev@lists.llvm.org> wrote: > I temporarily skipped these tests on Darwin and Linux here: > r255549 > > I'll file a bug in a moment... > > On Mon, Dec 14, 2015 at 1:42 PM, Todd Fiala

Re: [lldb-dev] debug info test failures

Okay. I appeared to be up to date when hitting it, but we may have crossed on it. I'll take out the skip if I am not hitting it now. Thanks! On Mon, Dec 14, 2015 at 2:01 PM, Zachary Turner wrote: > I believe I already fixed this issue > > On Mon, Dec 14, 2015 at 1:53 PM

[lldb-dev] [Bug 25825] TestWithLimitDebugInfo.py causing error

https://llvm.org/bugs/show_bug.cgi?id=25825 Todd Fiala changed: What|Removed |Added Status|NEW |RESOLVED