[lldb] Skip several lldb tests that are flaky on Windows

[stella.stamenova]

Summary

These tests fail every 10 or so runs on Windows causing both local failures as well as buildbot failures.

lldb/test/API/commands/process/attach/TestProcessAttach.py

def test_attach_to_process_by_name(self):
 
         self.runCmd("process attach -n " + exe_name)
 
         target = self.dbg.GetSelectedTarget()
 
         process = target.GetProcess()
         self.assertTrue(process, PROCESS_IS_VALID)
 
+    @skipIfWindows # This test is flaky on Windows
     @expectedFailureNetBSD
     def test_attach_to_process_by_id_correct_executable_offset(self):
         """
         Test that after attaching to a process the executable offset
         is determined correctly on FreeBSD.  This is a regression test
         for dyld plugin getting the correct executable path,
         and therefore being able to identify it in the module list.
         """

lldb/test/API/commands/target/auto-install-main-executable/TestAutoInstallMainExecutable.py

 from lldbsuite.test import lldbutil
 
 
 class TestAutoInstallMainExecutable(TestBase):
     mydir = TestBase.compute_mydir(__file__)
     NO_DEBUG_INFO_TESTCASE = True
 
     @skipIfRemote
+    @skipIfWindows # This test is flaky on Windows
     def test_target_auto_install_main_executable(self):
         if lldbgdbserverutils.get_lldb_server_exe() is None:
           self.skipTest("lldb-server not found")
         self.build()
 
         hostname = socket.getaddrinfo("localhost", 0, proto=socket.IPPROTO_TCP)[0][4][0]
         listen_url = "[%s]:0"%hostname
 

lldb/test/API/tools/lldb-server/TestGdbRemoteAttachOrWait.py

 
 import os
 from time import sleep
 
 import gdbremote_testcase
 import lldbgdbserverutils
 from lldbsuite.test.decorators import *
 from lldbsuite.test.lldbtest import *
 from lldbsuite.test import lldbutil
 
 
 class TestGdbRemoteAttachOrWait(gdbremote_testcase.GdbRemoteTestCaseBase):
 
     mydir = TestBase.compute_mydir(__file__)
 
+    @skipIfWindows # This test is flaky on Windows
     def test_launch_before_attach_with_vAttachOrWait(self):
         exe = '%s_%d' % (self.testMethodName, os.getpid())
         self.build(dictionary={'EXE': exe})
         self.set_inferior_startup_attach_manually()
 
         # Start the inferior, start the debug monitor, nothing is attached yet.
         procs = self.prep_debug_monitor_and_inferior(
             inferior_args=["sleep:60"],
def test_launch_before_attach_with_vAttachOrWait(self):
         self.assertIsNotNone(process_info)
 
         # Ensure the process id matches what we expected.
         pid_text = process_info.get('pid', None)
         self.assertIsNotNone(pid_text)
         reported_pid = int(pid_text, base=16)
         self.assertEqual(reported_pid, inferior.pid)
 
+    @skipIfWindows # This test is flaky on Windows
     def test_launch_after_attach_with_vAttachOrWait(self):
         exe = '%s_%d' % (self.testMethodName, os.getpid())
         self.build(dictionary={'EXE': exe})
         self.set_inferior_startup_attach_manually()
 
         server = self.connect_to_debug_monitor()
         self.assertIsNotNone(server)
 

lldb/test/API/tools/lldb-server/TestGdbRemoteAttachWait.py

 
 import os
 from time import sleep
 
 import gdbremote_testcase
 import lldbgdbserverutils
 from lldbsuite.test.decorators import *
 from lldbsuite.test.lldbtest import *
 from lldbsuite.test import lldbutil
 
 
 class TestGdbRemoteAttachWait(gdbremote_testcase.GdbRemoteTestCaseBase):
 
     mydir = TestBase.compute_mydir(__file__)
 
+    @skipIfWindows # This test is flaky on Windows
     def test_attach_with_vAttachWait(self):
         exe = '%s_%d' % (self.testMethodName, os.getpid())
 
         def launch_inferior():
             inferior = self.launch_process_for_attach(
                 inferior_args=["sleep:60"],
                 exe_path=self.getBuildArtifact(exe))
             self.assertIsNotNone(inferior)