Project Ortega BCM5719 LLVM https://git.raptorcs.com/git/bcm5719-llvm/atom?h=meklort-10.0.1 2015-10-28T17:43:26+00:00 2015-10-28T17:43:26+00:00 Zachary Turner zturner@google.com 2015-10-28T17:43:26+00:00 urn:sha1:c432c8f856e0bd84de980a9d9bb2d31b06fa95b1 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 2015-10-27T20:12:05+00:00 Zachary Turner zturner@google.com 2015-10-27T20:12:05+00:00 urn:sha1:0a0490b1520e96b728448b8c43ca873fcaa809dc llvm-svn: 251444 2015-10-26T17:52:16+00:00 Greg Clayton gclayton@apple.com 2015-10-26T17:52:16+00:00 urn:sha1:22fd3b1deeb447d2ecac8711b6e75ab4413336de The problem was that the @skipIfNoSBHeaders on darwin was trying to use self.lib_dir when it hadn't been set yet. I looked at the code and places were required to set "self.lib_dir" for no real reason as all places that used it just used the LLDB_LIB_DIR environment variable. So I removed all uses of self.lib_dir and replaced them to use 'os.environ["LLDB_LIB_DIR"]'. Did the same for self.implib_dir. llvm-svn: 251315 2015-10-23T17:04:29+00:00 Zachary Turner zturner@google.com 2015-10-23T17:04:29+00:00 urn:sha1:35d017f0fc38b53e31f1a44d07c3c142f5d3620b Apparently there were tons of instances I missed last time, I guess I accidentally ran 2to3 non-recursively. This should be every occurrence of a print statement fixed to use a print function as well as from __future__ import print_function being added to every file. After this patch print statements will stop working everywhere in the test suite, and the print function should be used instead. llvm-svn: 251121 2015-10-22T20:06:20+00:00 Zachary Turner zturner@google.com 2015-10-22T20:06:20+00:00 urn:sha1:77db4a855239049488e09f28c6665fdb3b51ef90 This is necessary in order to allow third party modules to be located under lldb/third_party rather than under the test folder directly. Since we're already touching every test file anyway, we also go ahead and delete the unittest2 import and main block wherever possible. The ability to run a test as a standalone file has already been broken for some time, and if we decide we want this back, we should use unittest instead of unittest2. A few places could not have the import of unittest2 removed,because they depend on the unittest2.expectedFailure or skip decorators. Removing all those was orthogonal in spirit to the purpose of this CL, so the import of unittest2 remains in those files that were using it for its test decorators. Those can be addressed separately. llvm-svn: 251055 2015-10-21T17:48:52+00:00 Zachary Turner zturner@google.com 2015-10-21T17:48:52+00:00 urn:sha1:814236d6947dfcc4773517449da1e626e0472d3c llvm-svn: 250915 2015-10-21T14:42:10+00:00 Adrian McCarthy amccarth@google.com 2015-10-21T14:42:10+00:00 urn:sha1:da9b90ce115f64210f9f428f7c3a8ae78a211a6c Differential Revision: http://reviews.llvm.org/D13923 llvm-svn: 250899 2015-09-14T14:42:22+00:00 Ed Maste emaste@freebsd.org 2015-09-14T14:42:22+00:00 urn:sha1:703c30904ec355074cf0044a737d39a376cbd310 One or more of these tests failed in 25 of 100 dotest.py runs. llvm-svn: 247566 2015-08-21T22:11:09+00:00 Zachary Turner zturner@google.com 2015-08-21T22:11:09+00:00 urn:sha1:28ee0cd30e409f67d48ff2b2624af517958e5e7d clang-cl does not yet support C++ exceptions, so these tests will not even compile. Re-enabling these tests is tracked by llvm.org/pr24538 llvm-svn: 245747 2015-07-01T22:50:28+00:00 Ying Chen chying@google.com 2015-07-01T22:50:28+00:00 urn:sha1:9b5eca903bbeb720ceb8e8e70824c9ec5794b56c llvm-svn: 241203