| Issue |
54728
|
| Summary |
[clang-tidy][run-clang-tidy.py] Uninformative error message after changes to binary discovery
|
| Labels |
new issue
|
| Assignees |
|
| Reporter |
neqochan
|
Commit 5da83eeb91bab848a096db7521c6d8be29231665 broke our clang-tidy invocation ([here](https://github.com/qogecoin/rules_ll/blob/a9dabb7d2c0d7dba93a100cbce3ee4717c5a1d85/ll/compilation_database.bzl#L87)).
I suspect that after the changes the automatic binary discovery somehow does not work with the `-clang-tidy-binary` option.
My issue is that the error message `Unable to run clang-tidy.` (from [here](https://github.com/llvm/llvm-project/blob/3b1314f4de63db771f1d93e1da06f14e7f3babab/clang-tools-extra/clang-tidy/tool/run-clang-tidy.py#L317)) is not very helpful for debugging (missing binary? threading issue? something else?) 😅. May be a bug as well. Currently looking into it and will post an update as soon as we find a fix on our side.
Tagging @SAtacker as you are the one who wrote this commit.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
