aboutsummaryrefslogtreecommitdiff
path: root/lldb/test/API/python_api
diff options
context:
space:
mode:
authorDavid Spickett <david.spickett@linaro.org>2024-05-29 10:05:43 +0000
committerDavid Spickett <david.spickett@linaro.org>2024-05-29 10:07:47 +0000
commit971f1aaad3ca3680bfbab76212f498ca15b280a2 (patch)
tree10d4576360944c5cb24a8bae84db6d5e0b0857af /lldb/test/API/python_api
parent5c214eb0c628c874f2c9496e663be4067e64442a (diff)
downloadllvm-971f1aaad3ca3680bfbab76212f498ca15b280a2.zip
llvm-971f1aaad3ca3680bfbab76212f498ca15b280a2.tar.gz
llvm-971f1aaad3ca3680bfbab76212f498ca15b280a2.tar.bz2
[lldb][Test][Windows] Fix flaky address range API tests
The new tests added in #92014 have been flaky on Linaro's Windows on Arm bot. They appear to be hitting a deadlock trying to clean up the test process. This only happens in async mode and I don't see why this test case needs async mode, so the simple workaround is to stick to sync mode.
Diffstat (limited to 'lldb/test/API/python_api')
-rw-r--r--lldb/test/API/python_api/address_range/TestAddressRange.py2
1 files changed, 0 insertions, 2 deletions
diff --git a/lldb/test/API/python_api/address_range/TestAddressRange.py b/lldb/test/API/python_api/address_range/TestAddressRange.py
index 8c27558..65221e3 100644
--- a/lldb/test/API/python_api/address_range/TestAddressRange.py
+++ b/lldb/test/API/python_api/address_range/TestAddressRange.py
@@ -15,8 +15,6 @@ class AddressRangeTestCase(TestBase):
self.build()
exe = self.getBuildArtifact("a.out")
- self.dbg.SetAsync(True)
-
self.target = self.dbg.CreateTarget(exe)
self.assertTrue(self.target, VALID_TARGET)
self.launch_info = self.target.GetLaunchInfo()