Re: [lldb-dev] mind if I try allowing reruns on arm/aarch64?

Great, thanks! Yes I was just checking after dinner and saw that it looks to be rerunning just fine. Okay I am likely to just strip out the serial test runner strategy at this point. One less thing to keep running. Thanks! -Todd On Thu, Dec 17, 2015 at 5:41 PM, Ying Chen wrote: > Hi Todd, >

Re: [lldb-dev] mind if I try allowing reruns on arm/aarch64?

Hi Todd, Seems the problem is fixed by using parallel runner. This test exits normally after rerun. http://lab.llvm.org:8011/builders/lldb-x86_64-ubuntu-14.04-android/builds/4357/steps/test7/logs/stdio On Thu, Dec 17, 2015 at 2:47 PM, Todd Fiala wrote: > Hi Ying, > > I just put this change in t

Re: [lldb-dev] building on mac

Ah. Okay, this might be the llvm/clang build script that Xcode uses as an llvm/clang build step. That's going to need to be updated if it is using configure (for the reasons I mentioned above). So it sounds like some part of llvm or clang may be sniffing and finding some part of ocaml, and decid

Re: [lldb-dev] building on mac

Does xcode use configure? I just push command-B. It does look like I have ocaml installed on my system, but I'm not sure how it go installed or why xcode is trying to use it. -- Ryan Brown On Thu, Dec 17, 2015 at 2:54 PM, Todd Fiala wrote: > We definitely should not be requiring ocaml :-) > > A

Re: [lldb-dev] building on mac

We definitely should not be requiring ocaml :-) Are you using a configure-based build? If so, can you switch over to using cmake and see if you see that same issue? We pretty much don't maintain the configure build, and it is getting stripped from llvm and clang in the next version of them after

Re: [lldb-dev] mind if I try allowing reruns on arm/aarch64?

Hi Ying, I just put this change in that reverted the aarch64 and arm removal from test-rerun eligibility: r255935. I'll watch this builder now and see what happens. If it hangs on reruns, I'll revert r255935. Thanks! -Todd

[lldb-dev] building on mac

Are there new prereqs for building on a mac? I just updated, and I'm getting this error: checking for __dso_handle... yes configure: WARNING: --enable-bindings=ocaml specified, but ctypes is not installed configure: WARNING: --enable-bindings=ocaml specified, but OUnit 2 is not installed. Tests

[lldb-dev] lists.llvm.org server maintenance, Friday Dec 18 @10:30 PST

All, The server that runs the mailing lists will be down for maintenance starting Friday Dec 18th at 10:30PM PST. I do not expect a long downtime, but please keep this in mind if you see any issues with the lists during this period. I will send an email once I am finished. No other services sh

Re: [lldb-dev] mind if I try allowing reruns on arm/aarch64?

Excellent. I'll try this in the afternoon. I need to run out now but I'll check in what we discussed later on when I get back. Thanks! On Thu, Dec 17, 2015 at 10:51 AM, Ying Chen wrote: > Yes, you could use android builder to run that experiment. > Please watch test 7 of this builder >

[lldb-dev] [Bug 25872] New: OS X: TestGlobalVariables dwarf is not finding the static const int g_file_static_int

https://llvm.org/bugs/show_bug.cgi?id=25872 Bug ID: 25872 Summary: OS X: TestGlobalVariables dwarf is not finding the static const int g_file_static_int Product: lldb Version: unspecified Hardware: PC OS: Ma

Re: [lldb-dev] mind if I try allowing reruns on arm/aarch64?

Yes, you could use android builder to run that experiment. Please watch test 7 of this builder after your change goes in(Another test for aarch64 which was previously timed out has been disabled for offline debugging of other unr

Re: [lldb-dev] mind if I try allowing reruns on arm/aarch64?

(And, as an aside, I may just nuke the serial test runner anyway, since we can do it with a multi-worker runner with a single worker just fine, and reduce the code size --- I really don't see a good reason to keep the serial test runner strategy anymore except for a purely theoretical sense). On T

[lldb-dev] mind if I try allowing reruns on arm/aarch64?

Hi Ying, I am speculating that the rerun logic issue where we saw the hang may be more of a serial test runner issue. Would you mind if I re-enabled the arm/aarch64 inclusion in the rerun logic now that I made a change based on this speculation? It would be a relatively quick way to check if the

[lldb-dev] [Bug 25869] New: OS X lldb crashed during test: ProcessGDBRemote/Broadcaster cleanup segfault

https://llvm.org/bugs/show_bug.cgi?id=25869 Bug ID: 25869 Summary: OS X lldb crashed during test: ProcessGDBRemote/Broadcaster cleanup segfault Product: lldb Version: unspecified Hardware: PC OS: MacOS X

[lldb-dev] [Bug 25866] New: Gentoo Linux build breaks in some scenarios when both Python 2 and Python 3 are present

https://llvm.org/bugs/show_bug.cgi?id=25866 Bug ID: 25866 Summary: Gentoo Linux build breaks in some scenarios when both Python 2 and Python 3 are present Product: lldb Version: unspecified Hardware: PC OS:

[lldb-dev] [Bug 25653] Cannot inspect const static variable

https://llvm.org/bugs/show_bug.cgi?id=25653 Ewan Crawford changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---