llvmorg-github-actions[bot] wrote:
<!--LLVM PR SUMMARY COMMENT--> @llvm/pr-subscribers-lldb Author: Charles Zablit (charles-zablit) <details> <summary>Changes</summary> 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`. --- Full diff: https://github.com/llvm/llvm-project/pull/207153.diff 1 Files Affected: - (modified) lldb/test/API/commands/platform/connect/TestPlatformConnect.py (+1-1) ``````````diff 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( `````````` </details> https://github.com/llvm/llvm-project/pull/207153 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
