[GH-ISSUE #1960] llvm-cov report is not correct for the trust-dns binary #831

New issue

Closed

opened 2026-03-16 00:28:34 +03:00 by kerem · 0 comments

kerem commented

2026-03-16 00:28:34 +03:00

Owner

Originally created by @bluejekyll on GitHub (Jun 5, 2023).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1960

Describe the bug

Code coverage reports are not reporting any coverage numbers for the trust-dns binary. I've verified (at least locally) that all the proper binary is being called with the LLVM_COV environment variables and a coverage report is being generated. The coverage remains rerooting 0 lines covered: https://app.codecov.io/gh/bluejekyll/trust-dns/tree/main/bin%2Fsrc

To Reproduce

run the just coverage command: html option available in just coverage-html #1959

Expected behavior

The trust-dns binary should be reporting some coverage of the lines executed, it's not clear why it is not. This probably points to other inaccuracies in the llvm-cov report generated by the cargo-llvm-cov command.

Originally created by @bluejekyll on GitHub (Jun 5, 2023). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1960 **Describe the bug** Code coverage reports are not reporting any coverage numbers for the `trust-dns` binary. I've verified (at least locally) that all the proper binary is being called with the LLVM_COV environment variables and a coverage report is being generated. The coverage remains rerooting 0 lines covered: https://app.codecov.io/gh/bluejekyll/trust-dns/tree/main/bin%2Fsrc **To Reproduce** run the `just coverage` command: html option available in `just coverage-html` #1959 **Expected behavior** The `trust-dns` binary should be reporting some coverage of the lines executed, it's not clear why it is not. This probably points to other inaccuracies in the `llvm-cov` report generated by the `cargo-llvm-cov` command.