summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/buildbot.py
Commit message (Collapse)AuthorAgeFilesLines
* [lldb/Scripts] Remove buildbot.pyJonas Devlieghere2020-01-101-196/+0
| | | | | This file is outdated and still references SVN. Buildbots are configured through the zorg repository.
* Python 2/3 compatibility: from __future__ import print_functionSerge Guelton2019-03-211-1/+1
| | | | | | Differential Revision: https://reviews.llvm.org/D59580 llvm-svn: 356695
* *** This commit represents a complete reformatting of the LLDB source codeKate Stone2016-09-061-39/+83
| | | | | | | | | | | | | | | | | | | | | | | *** to conform to clang-format’s LLVM style. This kind of mass change has *** two obvious implications: Firstly, merging this particular commit into a downstream fork may be a huge effort. Alternatively, it may be worth merging all changes up to this commit, performing the same reformatting operation locally, and then discarding the merge for this particular commit. The commands used to accomplish this reformatting were as follows (with current working directory as the root of the repository): find . \( -iname "*.c" -or -iname "*.cpp" -or -iname "*.h" -or -iname "*.mm" \) -exec clang-format -i {} + find . -iname "*.py" -exec autopep8 --in-place --aggressive --aggressive {} + ; The version of clang-format used was 3.9.0, and autopep8 was 1.2.4. Secondly, “blame” style tools will generally point to this commit instead of a meaningful prior commit. There are alternatives available that will attempt to look through this change and find the appropriate prior commit. YMMV. llvm-svn: 280751
* Added a buildbot script that automatically checksSean Callanan2011-10-141-0/+152
out the latest LLDB, LLVM and Clang and makes sure they work okay together. The buildbot is currently Mac OS X only because it uses xcodebuild. Right now, the portion that runs the LLDB test suite is commented out because of code-signing problems (specifically, on Mac OS 10.7 a UI dialog appears asking for the user's permission to attach to the inferior process). You can use the buildbot like this: ./scripts/buildbot.py -b /tmp/lldb-build -l /tmp/lldb.log /tmp/lldb-build and /tmp/lldb.log should not exist when the script is run. /tmp/lldb-build is a temporary directory and is removed at the end of a normal execution. /tmp/lldb.log is a log file that sticks around. The buildbot does not require built versions of anything; it will do the building itself. llvm-svn: 142006
OpenPOWER on IntegriCloud