An iteration on this that would be super interesting would be to have a bot report the data on the comment. One of the Ember Data maintainers did that for asset size for production builds of the library a couple years ago, and the TypeScript team has a bit to run builds generated from PRs against known outliers in the ecosystem to prevent significant regressions. In both cases, it’s incredibly handy to just have the info show up “inline” right where the other work and discussion is happening.
I think I tried using the LLVM instrumentation for generating code coverage data, but I think the issue for our projects was that we have a lot of FFI and of other libraries being linked, and just getting it to build was nightmarish. We use tarpaulin - it still has some issues, various weird segfaults were happening so we had to restrict what we get coverage for, but it’s quite straight-forward overall, and works fairly well with CodeCov. Maybe I should try again with LLVM, though.
An iteration on this that would be super interesting would be to have a bot report the data on the comment. One of the Ember Data maintainers did that for asset size for production builds of the library a couple years ago, and the TypeScript team has a bit to run builds generated from PRs against known outliers in the ecosystem to prevent significant regressions. In both cases, it’s incredibly handy to just have the info show up “inline” right where the other work and discussion is happening.
Oh that’s a great idea! I gave it a go here and it seems to be working nicely. Thanks for the idea!
🤩 cool! Also, it’s neat that it’s that easy to set up bot responses that way—I might have to do that with ideas like this myself in the future.
I think I tried using the LLVM instrumentation for generating code coverage data, but I think the issue for our projects was that we have a lot of FFI and of other libraries being linked, and just getting it to build was nightmarish. We use
tarpaulin- it still has some issues, various weird segfaults were happening so we had to restrict what we get coverage for, but it’s quite straight-forward overall, and works fairly well with CodeCov. Maybe I should try again with LLVM, though.Was that using https://github.com/taiki-e/cargo-llvm-cov? Someone sent me the link as a potential alternative to grcov.