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 origin/main...HEAD compiler-rt/test/lit.common.cfg.py
``````````
:warning:
The reproduction instructions above might return results for more than one PR
in a stack if you are using a stacked PR workflow. You can limit the results by
changing `origin/main` to the base branch/commit you want to compare against.
:warning:
</details>
<details>
<summary>
View the diff from darker here.
</summary>
``````````diff
--- lit.common.cfg.py 2025-10-26 08:38:20.000000 +0000
+++ lit.common.cfg.py 2025-10-26 08:39:43.808494 +0000
@@ -109,10 +109,11 @@
dynamic_library_lookup_var = "LD_LIBRARY_PATH_64"
new_ld_library_path_64 = os.path.pathsep.join(
(new_path, config.environment.get(dynamic_library_lookup_var, ""))
)
config.environment[dynamic_library_lookup_var] = new_ld_library_path_64
+
# TODO: Consolidate the logic for turning on the internal shell by default for
all LLVM test suites.
# See https://github.com/llvm/llvm-project/issues/106636 for more details.
#
# Choose between lit's internal shell pipeline runner and a real shell. If
``````````
</details>
https://github.com/llvm/llvm-project/pull/165148
_______________________________________________
llvm-branch-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-branch-commits
