03bdfb6561
A lot of `TestConcurrent*.py` expect one of the threads to crash, but we weren't checking for it properly. Possibly because signal reporting got better on FreeBSD at some point, and it now shows the same info as Linux does. ``` lldb-api :: functionalities/inferior-changed/TestInferiorChanged.py lldb-api :: functionalities/inferior-crashing/TestInferiorCrashing.py lldb-api :: functionalities/inferior-crashing/TestInferiorCrashingStep.py lldb-api :: functionalities/inferior-crashing/recursive-inferior/TestRecursiveInferior.py lldb-api :: functionalities/inferior-crashing/recursive-inferior/TestRecursiveInferiorStep.py lldb-api :: functionalities/thread/concurrent_events/TestConcurrentCrashWithBreak.py lldb-api :: functionalities/thread/concurrent_events/TestConcurrentCrashWithSignal.py lldb-api :: functionalities/thread/concurrent_events/TestConcurrentCrashWithWatchpoint.py lldb-api :: functionalities/thread/concurrent_events/TestConcurrentCrashWithWatchpointBreakpointSignal.py ``` Fixes #48777 `TestConcurrentTwoBreakpointsOneSignal.py` no longer fails, at least on an AWS instance, so I've removed the xfail there.
15 lines
546 B
Python
15 lines
546 B
Python
from lldbsuite.test.decorators import *
|
|
from lldbsuite.test.concurrent_base import ConcurrentEventsBase
|
|
from lldbsuite.test.lldbtest import TestBase
|
|
|
|
|
|
@skipIfWindows
|
|
class ConcurrentTwoBreakpointsOneSignal(ConcurrentEventsBase):
|
|
# Atomic sequences are not supported yet for MIPS in LLDB.
|
|
@skipIf(triple="^mips")
|
|
@expectedFlakeyNetBSD
|
|
def test(self):
|
|
"""Test two threads that trigger a breakpoint and one signal thread."""
|
|
self.build()
|
|
self.do_thread_actions(num_breakpoint_threads=2, num_signal_threads=1)
|