[Lldb-commits] [lldb] [lldb/linux] Make sure the process continues running after a detach (PR #88494)

[via lldb-commits]

github-actions[bot] wrote:

<!--LLVM CODE FORMAT COMMENT: {darker}-->


:warning: Python code formatter, darker found issues in your code. :warning:

<details>
<summary>
You can test this locally with the following command:
</summary>

``````````bash
darker --check --diff -r b88a1dd6c75754ace4abe18c8ea16a019f7b5529...9e1aca01da4a4aa5039c6ac1f8320f8c7d85b8e3 lldb/test/API/commands/process/detach-resumes/TestDetachResumes.py lldb/test/API/functionalities/fork/concurrent_vfork/TestConcurrentVFork.py
``````````

</details>

<details>
<summary>
View the diff from darker here.
</summary>

``````````diff
--- commands/process/detach-resumes/TestDetachResumes.py	2024-04-12 09:09:28.000000 +0000
+++ commands/process/detach-resumes/TestDetachResumes.py	2024-04-12 10:10:22.544874 +0000
@@ -6,10 +6,11 @@
 import lldb
 import time
 from lldbsuite.test.decorators import *
 from lldbsuite.test.lldbtest import *
 from lldbsuite.test import lldbutil
+
 
 class DetachResumesTestCase(TestBase):
     NO_DEBUG_INFO_TESTCASE = True
 
     def test_detach_resumes(self):
@@ -26,11 +27,13 @@
         # it.
         exit_file_path = lldbutil.append_to_process_working_directory(
             self, "exit_file_%d" % (int(time.time()))
         )
 
-        popen = self.spawnSubprocess(self.getBuildArtifact(exe), [sync_file_path, exit_file_path])
+        popen = self.spawnSubprocess(
+            self.getBuildArtifact(exe), [sync_file_path, exit_file_path]
+        )
         lldbutil.wait_for_file_on_target(self, sync_file_path)
 
         self.runCmd("process attach -p " + str(popen.pid))
 
         # Set a breakpoint at a place that will be called by multiple threads

``````````

</details>


https://github.com/llvm/llvm-project/pull/88494