-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Cannot run LLDB API Tests on MacOS #92603
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
Comments
@llvm/issue-subscribers-lldb Author: Valeriy Soltan (vsoltan)
Environment:
```
MacOS Sonoma 14.4.1 (23E224)
% lldb --version % which python3 % python3 --version % echo $PYTHONPATH
$ python3 During handling of the above exception, another exception occurred: Traceback (most recent call last):
% echo PYTHONPATH %which lldb % python3
% cmake -B build -G Ninja -C ./lldb/cmake/caches/Apple-lldb-macOS.cmake -DLLVM_ENABLE_PROJECTS="clang;lldb" -DCMAKE_BUILD_TYPE=Release -DLLVM_ENABLE_RUNTIMES="libcxx;libcxxabi;libunwind" ./llvm
UNRESOLVED: lldb-api :: commands/expression/import-std-module/vector-bool/TestVectorBoolFromStdModule.py (1006 of 2099)
|
Fix #92603 This replaces #113066. I finally came back to this issue and it seems that this approach is still very promising. As requested, I have added a short explanation as to why CPython module should be moved into a submodule. cc @JDevlieghere who reviewed on the previous PR earlier.
Fix llvm#92603 This replaces llvm#113066. I finally came back to this issue and it seems that this approach is still very promising. As requested, I have added a short explanation as to why CPython module should be moved into a submodule. cc @JDevlieghere who reviewed on the previous PR earlier.
Environment:
Minimal repro:
If I use the default installation of llvm (packaged with MacOS)
it works as intended.
What led to all of this is trying to run the lldb api tests docs
Similar Issues:
ModuleNotFoundError: No module named '_lldb'
with BuildType=Debug on Windows #87381 On Windows and debug configuration. Seems like the fix has been checked in. Similar issue ([LLDB] Most tests fail on Windows when built for debug #51272) suggested using the Release configuration instead of Debug; I'm seeing the issue onRelease
andReleaseWithDebInfo
The text was updated successfully, but these errors were encountered: