It seems Phab doesn't give you any context for this comment. For reference, this is in response to the comment:
Instead of duplicating the test, you could add a second run line in the other test and just verify that clang-tidy doesn't generate any warnings when run with -std=c99. The invariant "no warnings == no fixes" is pretty basic for clang-tidy, so you can rely on it in the tests. ~Aaron On Mon, Aug 31, 2015 at 10:17 AM, Aaron Ballman <aaron.ball...@gmail.com> wrote: > aaron.ballman marked an inline comment as done. > > ================ > Comment at: test/clang-tidy/misc-static-assert-c99.c:2 > @@ +1,3 @@ > +// RUN: %python %S/check_clang_tidy.py %s misc-static-assert %t -- -std=c99 > + > +void abort() {} > ---------------- > I am not certain how to accomplish this with the python script. Or are you > thinking I should run clang-tidy directly and use "| count 0" ? > > > http://reviews.llvm.org/D12446 > > > _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits