summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/default-constructor
diff options
context:
space:
mode:
authorEnrico Granata <egranata@apple.com>2015-10-30 01:09:54 +0000
committerEnrico Granata <egranata@apple.com>2015-10-30 01:09:54 +0000
commit8627209b43a430d4d91e93648bc1f30f93a756fc (patch)
treed5f6b0bc3488fdaa234f7557765fdc2c8493ad5a /lldb/packages/Python/lldbsuite/test/python_api/default-constructor
parent17f0275d4c2ea19b5a2376e3b008c41f18358d31 (diff)
downloadbcm5719-llvm-8627209b43a430d4d91e93648bc1f30f93a756fc.tar.gz
bcm5719-llvm-8627209b43a430d4d91e93648bc1f30f93a756fc.zip
Some test cases that need the lldbExec path were failing because lldbExec was turning out to be None even though it was being validly set by dotest.py
It turns out that lldbtest_config was being imported locally to "lldbsuite.test" instead of globally, so when the test cases got individually brought by a global import via __import__ by unittest2, they did not see the lldbtest_config import, and ended up importing a new separate copy of it, with lldbExec unset This is a simple hackaround that brings lldbtest_config to global visibility and makes sure the configuration data is correctly shared llvm-svn: 251678
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/default-constructor')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud