[lldb] Fixed the DAP tests in case of a remote target

[slydiman]

These tests are based on dap_server which runs locally. These tests failed in case of Windows host and Linux target.

[llvmbot]

@llvm/pr-subscribers-lldb

Author: Dmitry Vasilyev (slydiman)

Changes

These tests are based on dap_server which runs locally. These tests failed in case of Windows host and Linux target.

---

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

2 Files Affected:

• (modified) lldb/test/API/tools/lldb-dap/completions/TestDAP_completions.py (+1)
• (modified) lldb/test/API/tools/lldb-dap/exception/TestDAP_exception.py (+1)

diff --git a/lldb/test/API/tools/lldb-dap/completions/TestDAP_completions.py b/lldb/test/API/tools/lldb-dap/completions/TestDAP_completions.py
index 2b3ec656c107a..3250a5093cac4 100644
--- a/lldb/test/API/tools/lldb-dap/completions/TestDAP_completions.py
+++ b/lldb/test/API/tools/lldb-dap/completions/TestDAP_completions.py
@@ -19,6 +19,7 @@ def verify_completions(self, actual_list, expected_list, not_expected_list=[]):
             self.assertNotIn(not_expected_item, actual_list)
 
     @skipIfWindows
+    @skipIfRemote
     @skipIf(compiler="clang", compiler_version=["<", "17.0"])
     def test_completions(self):
         """
diff --git a/lldb/test/API/tools/lldb-dap/exception/TestDAP_exception.py b/lldb/test/API/tools/lldb-dap/exception/TestDAP_exception.py
index 8c2c0154ba65c..58a67d8164368 100644
--- a/lldb/test/API/tools/lldb-dap/exception/TestDAP_exception.py
+++ b/lldb/test/API/tools/lldb-dap/exception/TestDAP_exception.py
@@ -9,6 +9,7 @@
 
 
 class TestDAP_exception(lldbdap_testcase.DAPTestCaseBase):
+    @skipIfRemote
     @skipIfWindows
     def test_stopped_description(self):
         """

[labath]

Are all lldb-dap tests not compatible with running remotely? If so, then instead of annotating them individually, we could tag them all with some "dap" category (if they're not already) and then automatically skip that category when running remotely.

[walter-erquinigo]

That's a great idea. There's no such dap category at the moment, but it would be nice if such category is created as part of the ongoing lldb-dap test fixes.