Files
clang-p2996/lldb/test/API/api/multiple-targets/TestMultipleTargets.py
Jason Molenda 6d6feaf7e3 [lldb][NFC] update API tests which skip/expect-fail arm
The architectures provided to skipIf / expectedFail are regular
expressions (v. _match_decorator_property() in decorators.py
so on Darwin systems "arm64" would match the skips for "arm" (32-bit
Linux).  Update these to "arm$" to prevent this, and also update
three tests (TestBuiltinFormats.py, TestCrossDSOTailCalls.py,
TestCrossObjectTailCalls.py) that were skipped for arm64 via this
behavior, and need to be skipped or they will fail.

This was moviated by the new TestDynamicValue.py test which has
an expected-fail for arm, but the test was passing on arm64 Darwin
resulting in failure for the CIs.
2025-05-27 18:41:16 -07:00

30 lines
1.0 KiB
Python

"""Test the lldb public C++ api when creating multiple targets simultaneously."""
import os
import lldb
from lldbsuite.test.decorators import *
from lldbsuite.test.lldbtest import *
from lldbsuite.test import lldbutil
class TestMultipleTargets(TestBase):
NO_DEBUG_INFO_TESTCASE = True
@skipIf(oslist=["linux"], archs=["arm$", "aarch64"])
@skipIfNoSBHeaders
@expectedFailureAll(
oslist=["windows"], archs=["i[3-6]86", "x86_64"], bugnumber="llvm.org/pr20282"
)
@expectedFlakeyNetBSD
@skipIfHostIncompatibleWithTarget
def test_multiple_targets(self):
self.driver_exe = self.getBuildArtifact("multi-target")
self.buildDriver("main.cpp", self.driver_exe)
self.addTearDownHook(lambda: os.remove(self.driver_exe))
# check_call will raise a CalledProcessError if the executable 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.
subprocess.check_call([self.driver_exe, self.driver_exe])