diff options
| author | bors <bors@rust-lang.org> | 2025-04-26 22:33:56 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-04-26 22:33:56 +0000 |
| commit | 43e62a789c772642f79086f2cceef171cff30e63 (patch) | |
| tree | 21841e52831435447865e274efb0174365ec0fa2 /compiler/rustc_const_eval/src | |
| parent | 10fa3c449f6b1613b352a6cbf78d3d91fd9a1d81 (diff) | |
| parent | 1670de40e070e66e8074e1d534fd4acfa72acc39 (diff) | |
| download | rust-43e62a789c772642f79086f2cceef171cff30e63.tar.gz rust-43e62a789c772642f79086f2cceef171cff30e63.zip | |
Auto merge of #140288 - Zalathar:new-executor, r=jieyouxu
compiletest: Re-land using the new non-libtest executor by default This PR re-lands #139998, which had the misfortune of triggering download-rustc in its CI jobs, so we didn't get proper test metrics for comparison with the old implementation. So that was PR was reverted in #140233, with the intention of re-landing it alongside a dummy compiler change to inhibit download-rustc. --- Original PR description for #139998: >The new executor was implemented in #139660, but required a manual opt-in. This PR activates the new executor by default, but leaves the old libtest-based executor in place (temporarily) to make reverting easier if something unexpectedly goes horribly wrong. > >Currently the new executor can be explicitly disabled by passing the `-N` flag to compiletest (e.g. `./x test ui -- -N`), but eventually that flag will be removed, alongside the removal of the libtest dependency. The flag is mostly there to make manual comparative testing easier if something does go wrong. > >As before, there *should* be no user-visible difference between the old executor and the new executor. --- r? jieyouxu
Diffstat (limited to 'compiler/rustc_const_eval/src')
0 files changed, 0 insertions, 0 deletions
