[llvm-dev] A new code coverage bot

Philip Reames via llvm-dev llvm-dev at lists.llvm.org
Sat Sep 24 15:56:32 PDT 2016

I noticed that certain files which exist in ToT don't appear to be 
getting mentioned despite having test coverage within the test suite.

As a particular example, consider 
lib/Transforms/Scalar/RewriteStatepointsForGC.cpp.  There may also be 
others, but that's the one I happened to notice.

It's particular weird in that the gcc runs do include this particular file.


On 09/22/2016 10:05 AM, Vedant Kumar via llvm-dev wrote:
> Hi,
> I'd like to announce a new code coverage bot:
>      http://lab.llvm.org:8080/coverage/coverage-reports/clang/index.html
> The purpose of the bot is to make high-quality coverage reports available to
> llvm developers, and to provide additional testing for clang's code coverage
> implementation.
> The coverage data clang generates allows the reporting tool to render execution
> counts for code regions nested within lines or macros. The tool is also capable
> of displaying coverage information for each instantiation of a function.
> The bot runs "check-{llvm,clang}" with an instrumented version of the latest
> top-of-tree compiler. It generates new reports roughly every four hours. These
> reports can be used to find dead code, find fishy code, and to gauge the
> effectiveness of our smoke tests.
> If you have any feedback about the bot or the coverage reports, please let me
> know!
> vedant
> p.s: There is already a coverage bot which runs "check-all" and uses gcov. If
> you'd prefer those reports, you can find them here --
>      http://llvm.org/reports/coverage/
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

More information about the llvm-dev mailing list