Rollup of 7 pull requests Successful merges: - rust-lang/rust#146861 (add extend_front to VecDeque with specialization like extend) - rust-lang/rust#148213 (Fix invalid tag closing when leaving expansion "original code") - rust-lang/rust#148292 (Un-shadow object bound candidate in `NormalizesTo` goal if self_ty is trait object) - rust-lang/rust#148528 (run-make tests: use edition 2024) - rust-lang/rust#148554 (Add regression test for issue 148542) - rust-lang/rust#148561 (Fix ICE from async closure variance) - rust-lang/rust#148563 (rustdoc-search: remove broken index special case) r? `@ghost` `@rustbot` modify labels: rollup
The run-make test suite
The run-make test suite contains tests which are the most flexible out of all the rust-lang/rust test suites. run-make tests can basically contain arbitrary code, and are supported by the run_make_support library.
Infrastructure
A run-make test is a test recipe source file rmake.rs accompanied by its parent directory (e.g. tests/run-make/foo/rmake.rs is the foo run-make test).
The implementation for collecting and building the rmake.rs recipes are in src/tools/compiletest/src/runtest.rs, in run_rmake_test.
The setup for the rmake.rs can be summarized as a 3-stage process:
-
First, we build the
run_make_supportlibrary in bootstrap as a tool lib. -
Then, we compile the
rmake.rs"recipe" linking the support library and its dependencies in, and provide a bunch of env vars. We setup a directory structure withinbuild/<target>/test/run-make/<test-name>/ rmake.exe # recipe binary rmake_out/ # sources from test sources copied overand copy non-
rmake.rsinput support files over tormake_out/. The support library is made available as an extern prelude. -
Finally, we run the recipe binary and set
rmake_out/as the working directory.