nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-01 15:01:51 +00:00
Code Issues Packages Projects Releases Wiki Activity
7b97a5ca84
rust/tests/coverage-map
History
Zalathar 230dd5b8c7 coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-28 09:33:48 +11:00
..
status-quo coverage: Consistently remove unused counter IDs from expressions/mappings 2023-10-28 09:33:48 +11:00
fn_sig_into_try.cov-map coverage: Consistently remove unused counter IDs from expressions/mappings 2023-10-28 09:33:48 +11:00
fn_sig_into_try.rs coverage: Add a test showing the inconsistent handling of function signatures 2023-10-21 11:53:27 +11:00
if.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
if.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
long_and_wide.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
long_and_wide.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
README.md Copy most of tests/run-coverage into tests/coverage-map/status-quo 2023-09-05 11:55:34 +10:00
trivial.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
trivial.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
unreachable.cov-map coverage: Regression test for functions with unreachable bodies 2023-10-01 14:44:27 +11:00
unreachable.rs coverage: Regression test for functions with unreachable bodies 2023-10-01 14:44:27 +11:00

README.md

The tests in ./status-quo were copied from tests/run-coverage in order to capture the current behavior of the instrumentor on non-trivial programs. The actual mappings have not been closely inspected.

Maintenance note

These tests can be sensitive to small changes in MIR spans or MIR control flow, especially in HIR-to-MIR lowering or MIR optimizations.

If you haven't touched the coverage code directly, and the run-coverage test suite still works, then it should usually be OK to just --bless these coverage mapping tests as necessary, without worrying too much about the exact changes.