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
3f91bdfdd50aa4eaf1d3e49cf797220cfeccaf16...aecc7f751328a11c12bb910b1e30cab41b98a146
lldb/test/API/macosx/arm64e-attach/TestArm64eAttach.py
``````````
</details>
<details>
<summary>
View the diff from darker here.
</summary>
``````````diff
--- TestArm64eAttach.py 2024-02-25 23:15:23.000000 +0000
+++ TestArm64eAttach.py 2024-02-25 23:17:50.411840 +0000
@@ -12,11 +12,11 @@
def test(self):
# Skip this test if not running on AArch64 target that supports PAC
if not self.isAArch64PAuth():
self.skipTest("Target must support pointer authentication.")
- packets = self.getBuildArtifact('packet.log')
+ packets = self.getBuildArtifact("packet.log")
self.expect('log enable -f "%s" gdb-remote packets' % packets)
self.build()
popen = self.spawnSubprocess(self.getBuildArtifact(), [])
@@ -25,14 +25,16 @@
target = self.dbg.CreateTarget("", "arm64", "", True, error)
listener = lldb.SBListener("my.attach.listener")
process = target.AttachToProcessWithID(listener, popen.pid, error)
self.assertSuccess(error)
self.assertTrue(process, PROCESS_IS_VALID)
- self.assertEqual(target.GetTriple().split('-')[0], "arm64e",
- "target triple is updated correctly")
+ self.assertEqual(
+ target.GetTriple().split("-")[0],
+ "arm64e",
+ "target triple is updated correctly",
+ )
error = process.Kill()
self.assertSuccess(error)
# Test debugserver behavior.
self.filecheck('platform shell cat "%s"' % packets, __file__)
# CHECK:
cputype:100000c;cpusubtype:2;ptrsize:8;ostype:macosx;vendor:apple;endian:little;
-
``````````
</details>
https://github.com/llvm/llvm-project/pull/82938
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
