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 .ci/compute_projects.py
.ci/compute_projects_test.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
--- compute_projects.py 2026-03-12 12:07:32.000000 +0000
+++ compute_projects.py 2026-03-12 12:09:28.674236 +0000
@@ -155,11 +155,19 @@
"openmp": "check-openmp",
"polly": "check-polly",
"lit": "check-lit",
}
-RUNTIMES = {"libcxx", "libcxxabi", "libunwind", "compiler-rt", "libc",
"flang-rt", "libclc"}
+RUNTIMES = {
+ "libcxx",
+ "libcxxabi",
+ "libunwind",
+ "compiler-rt",
+ "libc",
+ "flang-rt",
+ "libclc",
+}
# Meta projects are projects that need explicit handling but do not reside
# in their own top level folder. To add a meta project, the start of the path
# for the metaproject should be mapped to the name of the project below.
# Multiple paths can map to the same metaproject.
``````````
</details>
https://github.com/llvm/llvm-project/pull/186104
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
