[lldb] Fixed find-module.test in case of a remote target

[slydiman]

Changing from UNSUPPOERTED to XFAIL in #94165 break x86 linux host / Aarch64 linux target build https://lab.llvm.org/buildbot/#/builders/195/builds/1047

[llvmbot]

@llvm/pr-subscribers-lldb

Author: Dmitry Vasilyev (slydiman)

Changes

Changing from UNSUPPOERTED to XFAIL in #94165 break x86 linux host / Aarch64 linux target build https://lab.llvm.org/buildbot/#/builders/195/builds/1047

---

Full diff: https://github.com/llvm/llvm-project/pull/116198.diff

1 Files Affected:

• (modified) lldb/test/Shell/Minidump/Windows/find-module.test (+1-1)

diff --git a/lldb/test/Shell/Minidump/Windows/find-module.test b/lldb/test/Shell/Minidump/Windows/find-module.test
index fe457f4123522f..39d9dab4d346d6 100644
--- a/lldb/test/Shell/Minidump/Windows/find-module.test
+++ b/lldb/test/Shell/Minidump/Windows/find-module.test
@@ -1,7 +1,7 @@
 Test that we correctly find a PE/COFF file in our executable search path, and
 use it when opening minidumps.
 
-XFAIL: remote{{.*}}
+XFAIL: system-windows && remote-linux
 
 RUN: yaml2obj %S/Inputs/find-module.exe.yaml -o %T/find-module.exe
 RUN: yaml2obj %S/Inputs/find-module.dmp.yaml -o %T/find-module.dmp

[DavidSpickett]

So it was unsupported so it never ran on that bot. Then it was changed to xfail for remote, so it passed on one bot but was broken on another.

This change narrows the xfail to the one configuration that fails.

In that case, LGTM.