99451b4453
Summary: Moves lldbsuite tests to lldb/test/API.
This is a largely mechanical change, moved with the following steps:
```
rm lldb/test/API/testcases
mkdir -p lldb/test/API/{test_runner/test,tools/lldb-{server,vscode}}
mv lldb/packages/Python/lldbsuite/test/test_runner/test lldb/test/API/test_runner
for d in $(find lldb/packages/Python/lldbsuite/test/* -maxdepth 0 -type d | egrep -v "make|plugins|test_runner|tools"); do mv $d lldb/test/API; done
for d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-vscode -maxdepth 1 -mindepth 1 | grep -v ".py"); do mv $d lldb/test/API/tools/lldb-vscode; done
for d in $(find lldb/packages/Python/lldbsuite/test/tools/lldb-server -maxdepth 1 -mindepth 1 | egrep -v "gdbremote_testcase.py|lldbgdbserverutils.py|socket_packet_pump.py"); do mv $d lldb/test/API/tools/lldb-server; done
```
lldb/packages/Python/lldbsuite/__init__.py and lldb/test/API/lit.cfg.py were also updated with the new directory structure.
Reviewers: labath, JDevlieghere
Tags: #lldb
Differential Revision: https://reviews.llvm.org/D71151
43 lines
1.4 KiB
Python
43 lines
1.4 KiB
Python
"""Test the lldb public C++ api when creating multiple targets simultaneously."""
|
|
|
|
from __future__ import print_function
|
|
|
|
|
|
import os
|
|
|
|
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)
|