https://github.com/charles-zablit created 
https://github.com/llvm/llvm-project/pull/207153

In f31853255c300e07b93783425e40948cc0dfdb0f, this test was marked as expected 
failure only when running with `lldb-server.exe`. It shoulds not have been, it 
is still failing. Revert the decorator to `expectedFailureWindows`.

>From 9d419118132526cd9a6c12a7f14effd2cd793e94 Mon Sep 17 00:00:00 2001
From: Charles Zablit <[email protected]>
Date: Thu, 2 Jul 2026 11:06:23 +0100
Subject: [PATCH] [lldb][Windows] Mark test as expected failure

---
 lldb/test/API/commands/platform/connect/TestPlatformConnect.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lldb/test/API/commands/platform/connect/TestPlatformConnect.py 
b/lldb/test/API/commands/platform/connect/TestPlatformConnect.py
index e971dc135487d..93fa5a5da45ea 100644
--- a/lldb/test/API/commands/platform/connect/TestPlatformConnect.py
+++ b/lldb/test/API/commands/platform/connect/TestPlatformConnect.py
@@ -63,7 +63,7 @@ def test_platform_process_connect(self):
     @skipIfRemote
     @expectedFailureAll(hostoslist=["windows"], triple=".*-android")
     @skipIfDarwin  # lldb-server not found correctly
-    @expectedFailureWindowsAndNoLLDBServer()  # process modules not loaded
+    @expectedFailureWindows  # process modules not loaded
     # lldb-server platform times out waiting for the gdbserver port number to 
be
     # written to the pipe, yet it seems the gdbserver already has written it.
     @expectedFailureAll(

_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to