about summary refs log tree commit diff
path: root/tests/coverage/await_ready.coverage
AgeCommit message (Collapse)AuthorLines
2025-05-06coverage: Only merge adjacent coverage spansZalathar-1/+1
This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2024-12-23Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, ↵Zalathar-0/+1
r=wesleywiser" This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
2024-12-16Stabilize #[coverage] attributeltdk-1/+0
2024-12-05Stabilize noop_wakerEric Holk-1/+0
Co-authored-by: zachs18 <8355914+zachs18@users.noreply.github.com>
2024-09-10coverage: Extract `executor::block_on` from several async coverage testsZalathar-25/+12
By moving `block_on` to an auxiliary crate, we avoid having to keep a separate copy of it in every async test. (This also incorporates some small tweaks to the headers in `await_ready.rs`.)
2024-09-06coverage: Treat await similar to a macroJonathan Conder-2/+2
Currently `await` is only counted towards coverage if the containing function is suspended and resumed at least once. This is because it expands to code which contains a branch on the discriminant of `Poll`. By treating it like a branching macro (e.g. `assert!`), these implementation details will be hidden from the coverage results.
2024-09-06coverage: Add test to codify existing behaviorJonathan Conder-0/+38
Currently `await` is only counted towards coverage if the containing function is suspended and resumed at least once. A future commit will fix this and update the test to reflect the new behavior.