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
39303e24b6f628f3c080f1b54bd12383a55b9b3a...dfcd21afd11b6e384ece06f128636dde2c075ac6
lldb/test/API/functionalities/gdb_remote_client/TestGDBRemoteClient.py
lldb/test/API/functionalities/inline-stepping/TestInlineStepping.py
``````````
</details>
<details>
<summary>
View the diff from darker here.
</summary>
``````````diff
--- gdb_remote_client/TestGDBRemoteClient.py 2024-10-29 23:35:22.000000 +0000
+++ gdb_remote_client/TestGDBRemoteClient.py 2024-10-30 00:13:12.020549 +0000
@@ -138,11 +138,11 @@
# test.
# Also, even with the use-g-packet-for-reading lldb will sometimes
send p0
# early on to see if the packet is supported. So we can't say that
there
# will be NO p packets.
# But there certainly should be no p packets after the g packet.
-
+
self.read_registers(process)
print(f"\nPACKET LOG:\n{self.server.responder.packetLog}\n")
g_pos = 0
try:
g_pos = self.server.responder.packetLog.index("g")
@@ -155,11 +155,18 @@
except:
pass
# Make sure there aren't any `p` packets after the `g` packet:
self.assertEqual(
- 0, len([p for p in self.server.responder.packetLog[g_pos:] if
p.startswith("p")])
+ 0,
+ len(
+ [
+ p
+ for p in self.server.responder.packetLog[g_pos:]
+ if p.startswith("p")
+ ]
+ ),
)
def test_read_registers_using_p_packets(self):
"""Test reading registers using 'p' packets"""
self.dbg.HandleCommand(
``````````
</details>
https://github.com/llvm/llvm-project/pull/114158
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
