a0a328ed4f
The comment says that TestMultipleDebuggers was XFAILed because it was failing nondeterministically in which case it should be skipped not failed (as XPASS will cause the test suite to fail). The reason it fails is because it was not marked as a no-debug-info test case. I've ran the test in a loop and it has been passing consistently. Let's enable it and see if the bots agree, if not we can skip it.
44 lines
1.5 KiB
Python
44 lines
1.5 KiB
Python
"""Test the lldb public C++ api when doing multiple debug sessions 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 TestMultipleSimultaneousDebuggers(TestBase):
|
|
|
|
mydir = TestBase.compute_mydir(__file__)
|
|
|
|
NO_DEBUG_INFO_TESTCASE = True
|
|
|
|
@skipIfNoSBHeaders
|
|
def test_multiple_debuggers(self):
|
|
env = {self.dylibPath: self.getLLDBLibraryEnvVal()}
|
|
|
|
self.driver_exe = self.getBuildArtifact("multi-process-driver")
|
|
self.buildDriver('multi-process-driver.cpp', self.driver_exe)
|
|
self.addTearDownHook(lambda: os.remove(self.driver_exe))
|
|
self.signBinary(self.driver_exe)
|
|
|
|
self.inferior_exe = self.getBuildArtifact("testprog")
|
|
self.buildDriver('testprog.cpp', self.inferior_exe)
|
|
self.addTearDownHook(lambda: os.remove(self.inferior_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.inferior_exe], env=env)
|
|
else:
|
|
with open(os.devnull, 'w') as fnull:
|
|
check_call([self.driver_exe, self.inferior_exe],
|
|
env=env, stdout=fnull, stderr=fnull)
|