[Lldb-commits] [lldb] Fix a couple of tests that were incorrectly using configuration.dwarf_version (PR #114161)

[via lldb-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 39303e24b6f628f3c080f1b54bd12383a55b9b3a...7fe3b6ac2e32dcb3660affa422ae8909b11670e2 lldb/packages/Python/lldbsuite/test/configuration.py lldb/test/API/lang/cpp/namespace/TestNamespaceLookup.py lldb/test/API/python_api/type/TestTypeList.py
``````````

</details>

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

``````````diff
--- test/API/lang/cpp/namespace/TestNamespaceLookup.py	2024-10-30 00:39:36.000000 +0000
+++ test/API/lang/cpp/namespace/TestNamespaceLookup.py	2024-10-30 00:46:35.813998 +0000
@@ -165,11 +165,14 @@
 
         # Continue to BP_file_scope at file scope
         self.runToBkpt("continue")
         # FIXME: In DWARF 5 with dsyms, the ordering of functions is slightly
         # different, which also hits the same issues mentioned previously.
-        if int(lldbplatformutil.getDwarfVersion()) <= 4 or self.getDebugInfo() == "dwarf":
+        if (
+            int(lldbplatformutil.getDwarfVersion()) <= 4
+            or self.getDebugInfo() == "dwarf"
+        ):
             self.expect_expr("func()", result_type="int", result_value="2")
 
         # Continue to BP_ns_scope at ns scope
         self.runToBkpt("continue")
         # Evaluate func(10) - should call A::func(int)

``````````

</details>


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