Author: David Spickett Date: 2023-02-23T14:10:07Z New Revision: dc2d2ca0603a5aaaea68515ff7c0605049268778
URL: https://github.com/llvm/llvm-project/commit/dc2d2ca0603a5aaaea68515ff7c0605049268778 DIFF: https://github.com/llvm/llvm-project/commit/dc2d2ca0603a5aaaea68515ff7c0605049268778.diff LOG: [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. Added: Modified: lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py Removed: ################################################################################ diff --git a/lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py b/lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py index c41446f96b8d7..e8805a68d33aa 100644 --- a/lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py +++ b/lldb/test/API/tools/lldb-server/TestGdbRemoteThreadsInStopReply.py @@ -171,6 +171,7 @@ def test_stop_reply_reports_correct_threads(self): 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() _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
