llvm-project/lldb/packages/Python/lldbsuite/test/plugins/builder_darwin.py


import lldbsuite.test.lldbtest as lldbtest

from builder_base import *

def buildDsym(
        sender=None,
        architecture=None,
        compiler=None,
        dictionary=None,
        testdir=None,
        testname=None):
    """Build the binaries with dsym debug info."""
    commands = []
    commands.append(getMake(testdir, testname) +
                    ["MAKE_DSYM=YES",
                     getArchSpec(architecture),
                     getCCSpec(compiler),
                     getDsymutilSpec(),
                     getSDKRootSpec(),
                     getModuleCacheSpec(),
                     "all",
                     getCmdLine(dictionary)])

    runBuildCommands(commands, sender=sender)

    # True signifies that we can handle building dsym.
    return True
Add from __future__ import print_function everywhere. 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-23 17:04:29 +00:00
Tighten up sys.path, and use absolute imports everywhere. For convenience, we had added the folder that dotest.py was in to sys.path, so that we could easily write things like `import lldbutil` from anywhere and any test. This introduces a subtle problem when using Python's package system, because when unittest2 imports a particular test suite, the test suite is detached from the package. Thus, writing "import lldbutil" from dotest imports it as part of the package, and writing the same line from a test does a fresh import since the importing module was not part of the same package. The real way to fix this is to use absolute imports everywhere. Instead of writing "import lldbutil", we need to write "import lldbsuite.test.util". This patch fixes up that and all other similar cases, and additionally removes the script directory from sys.path to ensure that this can't happen again. llvm-svn: 251886 2015-11-03 02:06:18 +00:00			`import lldbsuite.test.lldbtest as lldbtest`
Add a builder module for Linux (plus some refactoring) llvm-svn: 133457 2011-06-20 19:06:20 +00:00
			`from builder_base import *`

lldb should warn when dSYM does not match the binary. o Symbols.cpp: Emit a warning message when dSYM does not match the binary. o warnings/uuid: Added regression test case. o lldbtest.py: Modified to allow test case writer to demand that the build command does not begin with a clean first; required to make TestUUIDMismatchWanring.py work. rdar://problem/10515708 llvm-svn: 149465 2012-02-01 01:49:50 +00:00			`def buildDsym(`
			`sender=None,`
			`architecture=None,`
			`compiler=None,`
			`dictionary=None,`
Build each testcase variant in its own subdirectory and remove the srcdir lock file This patch creates a <test>.dwarf, <test>.dwo, etc., build directory for each testcase variant. Most importantly, this eliminates the need for the per-test lock file in the source directory. Tests that are marked as NO_DEBUG_INFO_TESTCASE and build with buildDefault() are built in a <test>.default build directory. Differential Revision: https://reviews.llvm.org/D42763 llvm-svn: 324368 2018-02-06 18:22:51 +00:00			`testdir=None,`
			`testname=None):`
Add a builder module for Linux (plus some refactoring) llvm-svn: 133457 2011-06-20 19:06:20 +00:00			`"""Build the binaries with dsym debug info."""`
Make the test runner understand Windows command shell execution. Currently, the test runner makes the assumption that it will run commands through /bin/sh. This is obviously not true on Windows, so this patch abstracts this logic out somewhat. Instead of having the caller build the command string himself, the caller will now pass in argument list of the form [[a, b], [c, d], ...] which will get converted into a string of the form a b; c d or a b && c d, depending on the platform. Reviewed by: Todd Fiala Differential Revision: http://reviews.llvm.org/D4590 llvm-svn: 213669 2014-07-22 16:19:29 +00:00			`commands = []`
Build each testcase variant in its own subdirectory and remove the srcdir lock file This patch creates a <test>.dwarf, <test>.dwo, etc., build directory for each testcase variant. Most importantly, this eliminates the need for the per-test lock file in the source directory. Tests that are marked as NO_DEBUG_INFO_TESTCASE and build with buildDefault() are built in a <test>.default build directory. Differential Revision: https://reviews.llvm.org/D42763 llvm-svn: 324368 2018-02-06 18:22:51 +00:00			`commands.append(getMake(testdir, testname) +`
Compile the LLDB tests out-of-tree. This patch is the result of a discussion on lldb-dev, see http://lists.llvm.org/pipermail/lldb-dev/2018-January/013111.html for background. For each test (should be eventually: each test configuration) a separate build directory is created and we execute make VPATH=$srcdir/path/to/test -C $builddir/path/to/test -f $srcdir/path/to/test/Makefile -I $srcdir/path/to/test In order to make this work all LLDB tests need to be updated to find the executable in the test build directory, since CWD still points at the test's source directory, which is a requirement for unittest2. Although we have done extensive testing, I'm expecting that this first attempt will break a few bots. Please DO NOT HESITATE TO REVERT this patch in order to get the bots green again. We will likely have to iterate on this some more. Differential Revision: https://reviews.llvm.org/D42281 llvm-svn: 323803 2018-01-30 18:29:16 +00:00			`["MAKE_DSYM=YES",`
			`getArchSpec(architecture),`
			`getCCSpec(compiler),`
[lldb/Test] Pass Make arguments in invocation instead of environment The Darwin builder is passing some of the make arguments trough the environment instead of the command line. Update the dsym builder to do the same as the other variants. 2020-06-02 16:40:07 -07:00			`getDsymutilSpec(),`
			`getSDKRootSpec(),`
			`getModuleCacheSpec(),`
			`"all",`
			`getCmdLine(dictionary)])`
Make the test runner understand Windows command shell execution. Currently, the test runner makes the assumption that it will run commands through /bin/sh. This is obviously not true on Windows, so this patch abstracts this logic out somewhat. Instead of having the caller build the command string himself, the caller will now pass in argument list of the form [[a, b], [c, d], ...] which will get converted into a string of the form a b; c d or a b && c d, depending on the platform. Reviewed by: Todd Fiala Differential Revision: http://reviews.llvm.org/D4590 llvm-svn: 213669 2014-07-22 16:19:29 +00:00
surface build error content through test event system Summary: print build errors nicely in test output This test infrastructure change adds a new Python exception for test subject builds that fail. The output of the build command is captured and propagated to both the textual test output display code and to the test event system. The ResultsFormatter objects have been modified to do something more useful with this information. The xUnit formatter now replaces the non-informative Python build error stacktrace with the build error content. The curses ResultsFormatter prints a 'B' for build errors rather than 'E'. The xUnit output, in particular, makes it much easier for developers to track down test subject build errors that cause test failures when reports come in from CI. Reviewers: granata.enrico Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D20252 llvm-svn: 269525 2016-05-14 00:42:30 +00:00			`runBuildCommands(commands, sender=sender)`
Add a builder module for Linux (plus some refactoring) llvm-svn: 133457 2011-06-20 19:06:20 +00:00
			`# True signifies that we can handle building dsym.`
			`return True`