rust/tests/coverage/async.coverage, branch 1.85.1https://github.com/rust-lang/rust
http://git.dreamy.place/mirrors/rust/atom?h=1.85.12024-12-23T01:30:37+00:00Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, r=wesleywiser"2024-12-23T01:30:37+00:00ZalatharZalathar@users.noreply.github.com2024-12-22T03:26:54+00:00urn:sha1:87c2f9a5be900e835f3c41cec2886d54ec0ca012
This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing
changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
Stabilize #[coverage] attribute2024-12-17T02:07:06+00:00ltdkusr@ltdk.xyz2024-09-23T23:40:22+00:00urn:sha1:cb487cc2fa3c5ebfddd22d6721cf1669943c1774Stabilize noop_waker2024-12-05T22:14:17+00:00Eric Holkericholk@microsoft.com2024-11-16T01:42:09+00:00urn:sha1:72ce1ab42f3be927f6f039a592222e054a0b0eaf
Co-authored-by: zachs18 <8355914+zachs18@users.noreply.github.com>
coverage: Extract `executor::block_on` from several async coverage tests2024-09-10T06:08:36+00:00ZalatharZalathar@users.noreply.github.com2024-09-06T05:41:10+00:00urn:sha1:e96b4e479a3835d43d3c0bfd1028b5ac9d99cfec
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`.)
coverage: Treat await similar to a macro2024-09-06T05:01:59+00:00Jonathan Conderjono.conder@gmail.com2024-09-05T22:25:25+00:00urn:sha1:25d183057edcf5d24ba0dcc8d5222a2a954aa80f
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.
coverage: Extract hole spans from HIR instead of MIR2024-07-08T11:22:56+00:00ZalatharZalathar@users.noreply.github.com2024-07-01T03:29:54+00:00urn:sha1:63c04f05e60ce27311fc1b874907188616beb558
This makes it possible to treat more kinds of nested item/code as holes,
instead of being restricted to closures.
[AUTO_GENERATED] Migrate compiletest to use `ui_test`-style `//@` directives2024-02-22T16:04:04+00:00许杰友 Jieyou Xu (Joe)jieyouxu@outlook.com2024-02-22T12:10:29+00:00urn:sha1:6e48b96692d63a79a14563f27fe5185f122434f8Rollup merge of #120015 - Zalathar:format, r=dtolnay2024-01-21T05:38:37+00:00NadrierilNadrieril@users.noreply.github.com2024-01-21T05:38:37+00:00urn:sha1:e8678b1030c50173ff29d77eae215b1f8472571d
coverage: Format all coverage tests with `rustfmt`
As suggested by <https://github.com/rust-lang/rust/pull/119984#discussion_r1452856806>.
Test files in `tests/` are normally ignored by `x fmt`, but sometimes those files end up being run through `rustfmt` anyway, either by `rust-analyzer` or by hand.
When that happens, it's annoying to have to manually revert formatting changes that are unrelated to the actual changes being made. So it's helpful for the tests in the repository to already have standard formatting beforehand.
However, there are several coverage tests that deliberately use non-standard formatting, so that line counts reveal more information about where code regions begin and end. In those cases, we can use `#[rustfmt::skip]` to prevent that code from being disturbed.
``@rustbot`` label +A-code-coverage
Remove unnecessary `let`s and borrowing from `Waker::noop()` usage.2024-01-17T20:00:27+00:00Kevin Reidkpreid@switchb.org2024-01-15T00:25:43+00:00urn:sha1:c48cdfe8ee582e3e67c9ffc036d8046add812565
`Waker::noop()` now returns a `&'static Waker` reference, so it can be
passed directly to `Context` creation with no temporary lifetime issue.
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting2024-01-16T04:56:37+00:00ZalatharZalathar@users.noreply.github.com2024-01-16T02:40:01+00:00urn:sha1:f1494425bbb68e71f2bf3aa215fb71978b36acf2
These tests deliberately use non-standard formatting, so that the line
execution counts reported by `llvm-cov` reveal additional information about
where code regions begin and end.