From dc2d2ca0603a5aaaea68515ff7c0605049268778 Mon Sep 17 00:00:00 2001 From: David Spickett Date: Thu, 23 Feb 2023 14:08:01 +0000 Subject: [PATCH] [LLDB] Mark test_stop_reply_contains_thread_pcs as an expected failure on Windows This has been flaky on the Windows on Arm LLDB bot. https://lab.llvm.org/buildbot/#/builders/219/builds/826 Given that test_stop_reply_reports_multiple_threads is already expected to fail on Windows, this is not suprising. --- lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py | 1 + 1 file changed, 1 insertion(+) diff --git a/lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py b/lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py index c41446f..e8805a6 100644 --- a/lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py +++ b/lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py @@ -171,6 +171,7 @@ class TestGdbRemoteThreadsInStopReply( self.assertIn(tid, stop_reply_threads) @skipIfNetBSD + @expectedFailureAll(oslist=["windows"]) # Extra threads present def test_stop_reply_contains_thread_pcs(self): self.build() self.set_inferior_startup_launch() -- 2.7.4