maxjhandsome
/
llvm-project
forked from OSchip/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Releases Wiki Activity

[PythonTestSuite] Fix usage of InitializePrivate in PythonTestSuite 

llvm-svn: 356950
This commit is contained in:
Jonas Devlieghere 2019-03-25 21:07:53 +00:00
parent 800fe977d0
commit e3959de268
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
lldb/unittests/ScriptInterpreter/Python/PythonTestSuite.cpp
View File

@ -16,14 +16,19 @@
#include "PythonTestSuite.h"
using namespace lldb_private;
class TestScriptInterpreterPython : public ScriptInterpreterPython {
public:
using ScriptInterpreterPython::Initialize;
using ScriptInterpreterPython::InitializePrivate;
};
void PythonTestSuite::SetUp() {
FileSystem::Initialize();
HostInfoBase::Initialize();
// ScriptInterpreterPython::Initialize() depends on HostInfo being
// initializedso it can compute the python directory etc.
ScriptInterpreterPython::Initialize();
ScriptInterpreterPython::InitializePrivate();
TestScriptInterpreterPython::Initialize();
TestScriptInterpreterPython::InitializePrivate();
// Although we don't care about concurrency for the purposes of running
// this test suite, Python requires the GIL to be locked even for
@ -36,7 +41,7 @@ void PythonTestSuite::SetUp() {
void PythonTestSuite::TearDown() {
PyGILState_Release(m_gil_state);
ScriptInterpreterPython::Terminate();
TestScriptInterpreterPython::Terminate();
HostInfoBase::Terminate();
FileSystem::Terminate();
}