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 HEAD~1...HEAD
lldb/test/API/functionalities/thread/num_threads/TestNumThreads.py
``````````
</details>
<details>
<summary>
View the diff from darker here.
</summary>
``````````diff
--- TestNumThreads.py 2025-05-22 02:44:29.000000 +0000
+++ TestNumThreads.py 2025-05-22 02:47:37.902846 +0000
@@ -137,21 +137,27 @@
# "frame-format-unique" not the "frame-format". Make
# sure we don't do that...
setting_data = self.dbg.GetSetting("frame-format-unique")
setting_str = setting_data.GetStringValue(1000)
setting_str = "UNIQUE: " + setting_str
- lldb.SBDebugger.SetInternalVariable("frame-format-unique",
setting_str, self.dbg.GetInstanceName())
+ lldb.SBDebugger.SetInternalVariable(
+ "frame-format-unique", setting_str, self.dbg.GetInstanceName()
+ )
# Now that we are stopped, we should have 10 threads waiting in the
# thread3 function. All of these threads should show as one stack.
self.expect(
"thread backtrace unique",
"Backtrace with unique stack shown correctly",
- substrs=[expect_string, "UNIQUE:", "main.cpp:%d" %
self.thread3_before_lock_line],
+ substrs=[
+ expect_string,
+ "UNIQUE:",
+ "main.cpp:%d" % self.thread3_before_lock_line,
+ ],
)
# Make sure setting the unique flag in the command isn't
# persistent:
self.expect(
"thread backtrace",
"Backtrace unique is not sticky",
substrs=["UNIQUE:"],
- matching=False
+ matching=False,
)
``````````
</details>
https://github.com/llvm/llvm-project/pull/140993
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
