| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | Make new dotest.py executable | Pavel Labath | 2015-10-30 | 1 | -0/+0 |
| | | | | | llvm-svn: 251684 | ||||
| * | Some test cases that need the lldbExec path were failing because lldbExec ↵ | Enrico Granata | 2015-10-30 | 1 | -1/+4 |
| | | | | | | | | | | | 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 | ||||
| * | Move lldb/test to lldb/packages/Python/lldbsuite/test. | Zachary Turner | 2015-10-28 | 1 | -0/+2039 |
| This is the conclusion of an effort to get LLDB's Python code structured into a bona-fide Python package. This has a number of benefits, but most notably the ability to more easily share Python code between different but related pieces of LLDB's Python infrastructure (for example, `scripts` can now share code with `test`). llvm-svn: 251532 | |||||
 |
index : bcm5719-llvm | |
| Project Ortega BCM5719 LLVM | Raptor Computing Systems |
| summaryrefslogtreecommitdiffstats |
|