[lldb] Account for extra threads in TestGdbRemoteThreadsInStopReply on windows

After 9611282c, TestGdbRemoteThreadsInStopReply is not non-deterministic
-- instead it deterministically fails due to extra threads created by
std::thread thread pool.

Adjust the tests to account for that.
This commit is contained in:
Pavel Labath 2022-02-09 17:38:27 +01:00
parent afb446e8a6
commit 1046b726ad
1 changed files with 4 additions and 3 deletions

View File

@ -126,6 +126,7 @@ class TestGdbRemoteThreadsInStopReply(
self.assertIsNotNone(context)
@skipIfNetBSD
@expectedFailureAll(oslist=["windows"]) # Extra threads present
def test_stop_reply_reports_multiple_threads(self):
self.build()
self.set_inferior_startup_launch()
@ -165,7 +166,7 @@ class TestGdbRemoteThreadsInStopReply(
threads = self.parse_threadinfo_packets(context)
self.assertIsNotNone(threads)
self.assertEqual(len(threads), thread_count)
self.assertGreaterEqual(len(threads), thread_count)
# Ensure each thread in q{f,s}ThreadInfo appears in stop reply threads
for tid in threads:
@ -182,12 +183,12 @@ class TestGdbRemoteThreadsInStopReply(
stop_reply_pcs = results["thread_pcs"]
pc_register = results["pc_register"]
little_endian = results["little_endian"]
self.assertEqual(len(stop_reply_pcs), thread_count)
self.assertGreaterEqual(len(stop_reply_pcs), thread_count)
threads_info_pcs = self.gather_threads_info_pcs(pc_register,
little_endian)
self.assertEqual(len(threads_info_pcs), thread_count)
self.assertEqual(len(threads_info_pcs), len(stop_reply_pcs))
for thread_id in stop_reply_pcs:
self.assertIn(thread_id, threads_info_pcs)
self.assertEqual(int(stop_reply_pcs[thread_id], 16),