6 commits

Author	SHA1	Message	Date
许杰友 Jieyou Xu (Joe)	6e48b96692	[AUTO_GENERATED] Migrate compiletest to use ui_test-style //@ directives	2024-02-22 16:04:04 +00:00
Nadrieril	e8678b1030	Rollup merge of #120015 - Zalathar:format, r=dtolnay ... 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	2024-01-21 06:38:37 +01:00
Kevin Reid	c48cdfe8ee	Remove unnecessary lets and borrowing from Waker::noop() usage. ... `Waker::noop()` now returns a `&'static Waker` reference, so it can be passed directly to `Context` creation with no temporary lifetime issue.	2024-01-17 12:00:27 -08:00
Zalathar	f1494425bb	coverage: Add #[rustfmt::skip] to tests with non-standard formatting ... 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.	2024-01-16 15:56:37 +11:00
Zalathar	5764ccc5e8	coverage: Use Waker::noop in async tests	2023-12-15 17:17:20 +11:00
Zalathar	e9d04c5e24	coverage: Migrate tests/run-coverage into tests/coverage	2023-11-07 11:15:19 +11:00

Renamed from tests/run-coverage/async.coverage (Browse further)