[compiler-rt] [compiler-rt] [test] Fix using toolchains that rely on Clang default configs (PR #113491)

[via llvm-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 2002533802dbe74c82476e30d093baf6d4cdee50...b4eb8c95ca85b71e089c41c93d11a2b12285c9aa compiler-rt/test/lit.common.cfg.py
``````````

</details>

<details>
<summary>
View the diff from darker here.
</summary>

``````````diff
--- lit.common.cfg.py	2024-10-23 20:03:37.000000 +0000
+++ lit.common.cfg.py	2024-10-23 20:08:45.836943 +0000
@@ -995,11 +995,11 @@
 # preempt something we're looking to trap (e.g. _FORTIFY_SOURCE vs our ASAN).
 #
 # Only set this if we know we can still build for the target while disabling
 # default configs.
 if config.has_no_default_config_flag:
-  config.environment["CLANG_NO_DEFAULT_CONFIG"] = "1"
+    config.environment["CLANG_NO_DEFAULT_CONFIG"] = "1"
 
 if config.has_compiler_rt_libatomic:
   base_lib = os.path.join(config.compiler_rt_libdir, "libclang_rt.atomic%s.so"
                           % config.target_suffix)
   if sys.platform in ['win32'] and execute_external:

``````````

</details>


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