Re: [Lldb-commits] [lldb] r266033 - Restore the lazy initialization of ScriptInterpreterPython, which was lost as part of the SystemLifetimeManager work

2016-04-12 Thread Enrico Granata via lldb-commits
Yeah. I ended up tracking it down by hand. I am running one final run of tests and should have a commit going in very soon. Sent from my iPhone > On Apr 12, 2016, at 11:20 AM, Zachary Turner wrote: > > I think todd did some work to get the gtests working in Xcode. Is that not > working? >> O

Re: [Lldb-commits] [lldb] r266033 - Restore the lazy initialization of ScriptInterpreterPython, which was lost as part of the SystemLifetimeManager work

2016-04-12 Thread Zachary Turner via lldb-commits
I think todd did some work to get the gtests working in Xcode. Is that not working? On Tue, Apr 12, 2016 at 11:12 AM Enrico Granata wrote: > Is there any failure logs I can look at? > I am gonna guess the issue is simply that the unit test is assuming Python > to be initialized. Which is a bad as

Re: [Lldb-commits] [lldb] r266033 - Restore the lazy initialization of ScriptInterpreterPython, which was lost as part of the SystemLifetimeManager work

2016-04-12 Thread Enrico Granata via lldb-commits
Is there any failure logs I can look at? I am gonna guess the issue is simply that the unit test is assuming Python to be initialized. Which is a bad assumption after my change. Sent from my iPhone > On Apr 12, 2016, at 2:16 AM, Pavel Labath wrote: > > This breaks the python unit tests. Doesn

Re: [Lldb-commits] [lldb] r266033 - Restore the lazy initialization of ScriptInterpreterPython, which was lost as part of the SystemLifetimeManager work

2016-04-12 Thread Pavel Labath via lldb-commits
This breaks the python unit tests. Doesn't seem hard to fix, it seems we just need some way to "really" initialize python before we run the tests. However, I have reverted this change until that happens to keep to bots green. pl On 12 April 2016 at 02:41, Enrico Granata via lldb-commits < lldb-co

Re: [Lldb-commits] [lldb] r266033 - Restore the lazy initialization of ScriptInterpreterPython, which was lost as part of the SystemLifetimeManager work

2016-04-11 Thread Enrico Granata via lldb-commits
> On Apr 11, 2016, at 6:28 PM, Zachary Turner wrote: > > I have a feeling this breaks something, but I'm not sure what. I remember > specifically needing this for some reason. > If you manage to repro the breakage, let’s work on getting it fixed I’d like to not have to initialize Python eager

Re: [Lldb-commits] [lldb] r266033 - Restore the lazy initialization of ScriptInterpreterPython, which was lost as part of the SystemLifetimeManager work

2016-04-11 Thread Zachary Turner via lldb-commits
I have a feeling this breaks something, but I'm not sure what. I remember specifically needing this for some reason. Did you verify that the gtest suite as well as the dotest suite and the interactive interpreter all still pass / work? On Mon, Apr 11, 2016 at 6:14 PM Enrico Granata via lldb-commit

[Lldb-commits] [lldb] r266033 - Restore the lazy initialization of ScriptInterpreterPython, which was lost as part of the SystemLifetimeManager work

2016-04-11 Thread Enrico Granata via lldb-commits
Author: enrico Date: Mon Apr 11 20:08:35 2016 New Revision: 266033 URL: http://llvm.org/viewvc/llvm-project?rev=266033&view=rev Log: Restore the lazy initialization of ScriptInterpreterPython, which was lost as part of the SystemLifetimeManager work Modified: lldb/trunk/source/Plugins/Scri