[Lldb-commits] [lldb] [lldb] Fixed the test TestDyldLaunchLinux (PR #92080)

[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 c441aa51e16e2fa5f407191287f48d2b7c302ceb...a5b005cbbfd25c9fb3e59f2cb0f98c2f6a3e405d lldb/test/API/functionalities/dyld-launch-linux/TestDyldLaunchLinux.py
``````````

</details>

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

``````````diff
--- TestDyldLaunchLinux.py	2024-05-14 08:09:09.000000 +0000
+++ TestDyldLaunchLinux.py	2024-05-14 08:14:21.760387 +0000
@@ -38,13 +38,15 @@
             "// Break here", lldb.SBFileSpec("main.cpp")
         )
         breakpoint_shared_library = target.BreakpointCreateBySourceRegex(
             "get_signal_crash", lldb.SBFileSpec("signal_file.cpp")
         )
-        inferior_exe_path = lldbutil.install_to_target(self, self.getBuildArtifact("a.out"))
+        inferior_exe_path = lldbutil.install_to_target(
+            self, self.getBuildArtifact("a.out")
+        )
         lldbutil.install_to_target(self, self.getBuildArtifact("libsignal_file.so"))
-        
+
         launch_info = lldb.SBLaunchInfo(
             [
                 "--library-path",
                 self.get_process_working_directory(),
                 inferior_exe_path,

``````````

</details>


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