[flang-commits] [flang] [Flang][test] Account for FLANG_TEST_Fortran_FLAGS (PR #213964)

[via flang-commits]

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 flang/test/lit.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.cfg.py	2026-08-06 10:39:13.000000 +0000
+++ lit.cfg.py	2026-08-06 10:40:55.718478 +0000
@@ -218,11 +218,11 @@
 ]
 
 # Some tests expect the command line to be verbatim what is specified on the
 # RUN: line.
 if not flang_extra_search_args:
-  config.available_features.add("flang-authentic-cmdline")
+    config.available_features.add("flang-authentic-cmdline")
 
 # Flang has several unimplemented features. TODO messages are used to mark
 # and fail if these features are exercised. Some TODOs exit with a non-zero
 # exit code, but others abort the execution in assert builds.
 # To catch aborts, the `--crash` option for the `not` command has to be used.

``````````

</details>


https://github.com/llvm/llvm-project/pull/213964