This script is meant to be run on code coverage bots in conjunction with utils/prepare-code-coverage-artifact.py to flag coverage regressions in a window of commits.
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
- Added doctests.
- Improved comments.
- Fixed an issue where we would exit(0) even if there are regressions.
Comment Actions
lgtm, seems handy.
Is this something that you intend to ship to users, or just a tool for tracking LLVM coverage?
Comment Actions
lgtm, seems handy.
Is this something that you intend to ship to users, or just a tool for tracking LLVM coverage?
Comment Actions
Thanks. @cmatthews and I are working on a bot to track coverage regressions in llvm. The plan is to let people hammer out usability issues with internal bots (at least, that's what we're doing) and then see if there's broader interest.
I don't know what shipping this script to users entails. It doesn't bake in assumptions about the llvm codebase, if that's what you mean.