mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2025-04-14 12:22:27 +00:00
5ec76fe720
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
45 lines
1.4 KiB
Python
45 lines
1.4 KiB
Python
"""Test the lldb public C++ api when creating multiple targets simultaneously."""
|
|
|
|
from __future__ import print_function
|
|
|
|
|
|
import os
|
|
import re
|
|
import subprocess
|
|
|
|
import lldb
|
|
from lldbsuite.test.decorators import *
|
|
from lldbsuite.test.lldbtest import *
|
|
from lldbsuite.test import lldbutil
|
|
|
|
|
|
class TestMultipleTargets(TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
NO_DEBUG_INFO_TESTCASE = True
|
|
|
|
@skipIfNoSBHeaders
|
|
@skipIfHostIncompatibleWithRemote
|
|
@expectedFailureAll(
|
|
oslist=["windows", "freebsd"],
|
|
bugnumber="llvm.org/pr20282")
|
|
def test_multiple_targets(self):
|
|
env = {self.dylibPath: self.getLLDBLibraryEnvVal()}
|
|
|
|
self.driver_exe = self.getBuildArtifact("multi-target")
|
|
self.buildDriver('main.cpp', self.driver_exe)
|
|
self.addTearDownHook(lambda: os.remove(self.driver_exe))
|
|
self.signBinary(self.driver_exe)
|
|
|
|
# check_call will raise a CalledProcessError if multi-process-driver doesn't return
|
|
# exit code 0 to indicate success. We can let this exception go - the test harness
|
|
# will recognize it as a test failure.
|
|
|
|
if self.TraceOn():
|
|
print("Running test %s" % self.driver_exe)
|
|
check_call([self.driver_exe, self.driver_exe], env=env)
|
|
else:
|
|
with open(os.devnull, 'w') as fnull:
|
|
check_call([self.driver_exe, self.driver_exe],
|
|
env=env, stdout=fnull, stderr=fnull)
|