Skip to content

[lldb][test] Provide proper path to LLVM utils in API tests #110837

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 7, 2024

Conversation

dzhidzhoev
Copy link
Member

In aea0668, API tests were supposed to use LLVM tools.
However, a path to a utility is made up incorrectly there: util name should be prefixed with llvm-.

Hence, it's fixed here.

@dzhidzhoev dzhidzhoev added the lldb label Oct 2, 2024
@dzhidzhoev dzhidzhoev self-assigned this Oct 2, 2024
@llvmbot
Copy link
Member

llvmbot commented Oct 2, 2024

@llvm/pr-subscribers-lldb

Author: Vladislav Dzhidzhoev (dzhidzhoev)

Changes

In aea0668, API tests were supposed to use LLVM tools.
However, a path to a utility is made up incorrectly there: util name should be prefixed with llvm-.

Hence, it's fixed here.


Full diff: https://github.com/llvm/llvm-project/pull/110837.diff

1 Files Affected:

  • (modified) lldb/packages/Python/lldbsuite/test/builders/builder.py (+1-1)
diff --git a/lldb/packages/Python/lldbsuite/test/builders/builder.py b/lldb/packages/Python/lldbsuite/test/builders/builder.py
index e3099219e437e3..d5321f13b47488 100644
--- a/lldb/packages/Python/lldbsuite/test/builders/builder.py
+++ b/lldb/packages/Python/lldbsuite/test/builders/builder.py
@@ -153,7 +153,7 @@ def getToolchainSpec(self, compiler):
         cc_dir = cc_path.parent
 
         def getToolchainUtil(util_name):
-            return os.path.join(configuration.llvm_tools_dir, util_name + exe_ext)
+            return os.path.join(configuration.llvm_tools_dir, "llvm-" + util_name + exe_ext)
 
         cxx = cc_dir / (cc_prefix + cxx_type + cc_ext)
 

Copy link

github-actions bot commented Oct 2, 2024

✅ With the latest revision this PR passed the Python code formatter.

@dzhidzhoev dzhidzhoev force-pushed the lldb/proper-llvm-utils-path branch from 2036458 to 8deb61b Compare October 2, 2024 13:09
In aea0668, API tests were supposed to be switched to LLVM tools
usage.
However, a path to an utility is made up incorrectly there: util name
should be prefixed with `llvm-`.

Hence it is fixed here.
@dzhidzhoev dzhidzhoev force-pushed the lldb/proper-llvm-utils-path branch from 8deb61b to a2c8b8b Compare October 2, 2024 13:17
@dzhidzhoev dzhidzhoev merged commit e7174a8 into llvm:main Oct 7, 2024
7 checks passed
DavidSpickett added a commit that referenced this pull request Oct 8, 2024
Originally failing due to #24901,
but since #110837 the
test is passing.

https://lab.llvm.org/buildbot/#/builders/141/builds/3012

My guess is that the `llvm-` tool has better support for static
libraries on Windows.
DavidSpickett added a commit that referenced this pull request Oct 8, 2024
Originally failing due to #24901,
but since #110837 the
test is passing.

Already removed one xfail but didn't realise we had more for
the same bug.
@dzhidzhoev
Copy link
Member Author

@DavidSpickett thank you for the fixes!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants