We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
check-mlir
With CMake config:
-DLLVM_ENABLE_PROJECTS="mlir;clang" -DLLVM_BUILD_EXAMPLES=ON -DLLVM_ENABLE_ASSERTIONS=ON -DLLVM_CCACHE_BUILD=ON -DLLVM_ENABLE_LLD=ON -DLLVM_USE_SANITIZER="Address;Undefined" -DMLIR_INCLUDE_INTEGRATION_TESTS=ON -DLLVM_USE_SPLIT_DWARF=ON -DBUILD_SHARED_LIBS=ON -DCLANG_ENABLE_CIR=ON
and clang compiler on macOS, check-mlir got error message:
[804/805] Running the MLIR regression tests llvm-lit: /Volumes/nvme/projects/llvm-project/llvm/utils/lit/lit/TestingConfig.py:156: fatal: unable to parse config file '/Volumes/nvme/projects/llvm-project/mlir/test/lit.cfg.py', traceback: Traceback (most recent call last): File "/Volumes/nvme/projects/llvm-project/llvm/utils/lit/lit/TestingConfig.py", line 144, in load_from_path exec(compile(data, path, "exec"), cfg_globals, None) ~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/Volumes/nvme/projects/llvm-project/mlir/test/lit.cfg.py", line 254, in <module> real_python_executable = find_real_python_interpreter() File "/Volumes/nvme/projects/llvm-project/mlir/test/lit.cfg.py", line 109, in find_real_python_interpreter copied_python = os.path.join(config.lldb_build_directory, "copied-python") ^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'TestingConfig' object has no attribute 'lldb_build_directory'
Is this a bug of the script or some misconfig of my environment?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
With CMake config:
and clang compiler on macOS,
check-mlir
got error message:Is this a bug of the script or some misconfig of my environment?
The text was updated successfully, but these errors were encountered: