While this doesn't slow down a fresh build by much, this is disastrous when jumping between branches as none of the results are cached and they all need to be recomputed.
Details
Details
- Reviewers
Fabien - Group Reviewers
Restricted Project - Commits
- rSTAGING33c735931731: Disable clang-tidy by default
rABC33c735931731: Disable clang-tidy by default
Run ninja clean and then ninja with clang-tidy:
real 1m22.667s user 11m38.143s sys 0m37.996s
Now the same without clang-tidy:
real 0m28.937s user 0m46.723s sys 0m10.769s
Diff Detail
Diff Detail
- Repository
- rABC Bitcoin ABC
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
Yeah I get the same kind of timings and as you say, jumping branches gets to be a headache... I caved in finally and turned off the option locally.
Comment Actions
I spent a lot of time trying to tweak ccache to make it understand clang-tidy as a compiler command but so far nothing worked.
This is reasonable to disable it by default for now.