| commit | ac2161005c658e06c05bd242a2009578ee8e2347 | |
| author | Andrey Alekseenko <al42and@gmail.com> | |
| Fri, 9 Oct 2020 14:23:34 +0000 (9 14:23 +0000) | ||
| committer | Artem Zhmurov <zhmurov@gmail.com> | |
| Fri, 9 Oct 2020 14:23:34 +0000 (9 14:23 +0000) | ||
| tree | 0edf56a3abfeb6437b058b1d1160274b477547e7 | treesnapshot (tar.gz zip) |
| parent | 457e3d820e7e0e388d50d04f81a6267eb236e3aa | commitdiff |
Try to fix the nightly clang-tidy-9 build
It appears that some of the `#ifdef __clang_analyzer__` patches in
gtest/gmock are now messing up with clang-tidy.
Probably related to https://reviews.llvm.org/D46325?
Here, we remove some of these special handlings of clang-analyzer, and
add a couple of more gentle NOLINT's. Since apparently we already had
patches in our copy of googletest, I don't feel bad about it.
Appears to work fine locally with clang-tidy-9.
It appears that some of the `#ifdef __clang_analyzer__` patches in
gtest/gmock are now messing up with clang-tidy.
Probably related to https://reviews.llvm.org/D46325?
Here, we remove some of these special handlings of clang-analyzer, and
add a couple of more gentle NOLINT's. Since apparently we already had
patches in our copy of googletest, I don't feel bad about it.
Appears to work fine locally with clang-tidy-9.