mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
rust/tests/coverage/attr/off-on-sandwich.cov-map

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

31 lines
1.1 KiB
Plaintext
Raw Permalink Normal View History

Add more thorough coverage tests for `#[coverage(..)]` in nested functions These tests reflect the current implementation behaviour, which is not necessarily the desired behaviour.
2024-06-18 05:02:21 -05:00
Function name: off_on_sandwich::dense_a::dense_b
coverage: Extract hole spans from HIR instead of MIR This makes it possible to treat more kinds of nested item/code as holes, instead of being restricted to closures.
2024-06-30 22:29:54 -05:00
Raw bytes (14): 0x[01, 01, 00, 02, 01, 0f, 05, 02, 12, 01, 07, 05, 00, 06]
Add more thorough coverage tests for `#[coverage(..)]` in nested functions These tests reflect the current implementation behaviour, which is not necessarily the desired behaviour.
2024-06-18 05:02:21 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
coverage: Extract hole spans from HIR instead of MIR This makes it possible to treat more kinds of nested item/code as holes, instead of being restricted to closures.
2024-06-30 22:29:54 -05:00
Number of file 0 mappings: 2
- Code(Counter(0)) at (prev + 15, 5) to (start + 2, 18)
- Code(Counter(0)) at (prev + 7, 5) to (start + 0, 6)
coverage: Include the highest counter ID seen in `.cov-map` dumps When making changes that have a large impact on coverage counter creation, this makes it easier to see whether the number of physical counters has changed. (The highest counter ID seen in coverage maps is not necessarily the same as the number of physical counters actually used by the instrumented code, but it's the best approximation we can get from looking only at the coverage maps, and it should be reasonably accurate in most cases.)
2024-10-07 21:13:05 -05:00
Highest counter ID seen: c0
Add more thorough coverage tests for `#[coverage(..)]` in nested functions These tests reflect the current implementation behaviour, which is not necessarily the desired behaviour.
2024-06-18 05:02:21 -05:00
Function name: off_on_sandwich::sparse_a::sparse_b::sparse_c
coverage: Extract hole spans from HIR instead of MIR This makes it possible to treat more kinds of nested item/code as holes, instead of being restricted to closures.
2024-06-30 22:29:54 -05:00
Raw bytes (14): 0x[01, 01, 00, 02, 01, 21, 09, 02, 17, 01, 0b, 09, 00, 0a]
Add more thorough coverage tests for `#[coverage(..)]` in nested functions These tests reflect the current implementation behaviour, which is not necessarily the desired behaviour.
2024-06-18 05:02:21 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
coverage: Extract hole spans from HIR instead of MIR This makes it possible to treat more kinds of nested item/code as holes, instead of being restricted to closures.
2024-06-30 22:29:54 -05:00
Number of file 0 mappings: 2
- Code(Counter(0)) at (prev + 33, 9) to (start + 2, 23)
- Code(Counter(0)) at (prev + 11, 9) to (start + 0, 10)
coverage: Include the highest counter ID seen in `.cov-map` dumps When making changes that have a large impact on coverage counter creation, this makes it easier to see whether the number of physical counters has changed. (The highest counter ID seen in coverage maps is not necessarily the same as the number of physical counters actually used by the instrumented code, but it's the best approximation we can get from looking only at the coverage maps, and it should be reasonably accurate in most cases.)
2024-10-07 21:13:05 -05:00
Highest counter ID seen: c0
Add more thorough coverage tests for `#[coverage(..)]` in nested functions These tests reflect the current implementation behaviour, which is not necessarily the desired behaviour.
2024-06-18 05:02:21 -05:00
Function name: off_on_sandwich::sparse_a::sparse_b::sparse_c::sparse_d
coverage: Extract hole spans from HIR instead of MIR This makes it possible to treat more kinds of nested item/code as holes, instead of being restricted to closures.
2024-06-30 22:29:54 -05:00
Raw bytes (14): 0x[01, 01, 00, 02, 01, 24, 0d, 02, 1b, 01, 07, 0d, 00, 0e]
Add more thorough coverage tests for `#[coverage(..)]` in nested functions These tests reflect the current implementation behaviour, which is not necessarily the desired behaviour.
2024-06-18 05:02:21 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
coverage: Extract hole spans from HIR instead of MIR This makes it possible to treat more kinds of nested item/code as holes, instead of being restricted to closures.
2024-06-30 22:29:54 -05:00
Number of file 0 mappings: 2
- Code(Counter(0)) at (prev + 36, 13) to (start + 2, 27)
- Code(Counter(0)) at (prev + 7, 13) to (start + 0, 14)
coverage: Include the highest counter ID seen in `.cov-map` dumps When making changes that have a large impact on coverage counter creation, this makes it easier to see whether the number of physical counters has changed. (The highest counter ID seen in coverage maps is not necessarily the same as the number of physical counters actually used by the instrumented code, but it's the best approximation we can get from looking only at the coverage maps, and it should be reasonably accurate in most cases.)
2024-10-07 21:13:05 -05:00
Highest counter ID seen: c0
Add more thorough coverage tests for `#[coverage(..)]` in nested functions These tests reflect the current implementation behaviour, which is not necessarily the desired behaviour.
2024-06-18 05:02:21 -05:00
Reference in New Issue Copy Permalink