Tracking issue for new compiletest executor #140192
Labels
A-compiletest
Area: The compiletest test runner
A-test-infra
Area: test infrastructure (may span bootstrap/compiletest/more)
C-tracking-issue
Category: An issue tracking the progress of sth. like the implementation of an RFC
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
This is a tracking issue for migrating towards a new compiletest executor to replace the dependency on the
libtest executor.
This tracking issue is not meant for discussions or bug reports but is meant to track implementation progress, please open individual issues for bugs / discussions or zulip threads instead.
Summary
compiletest
currently relies on the in-tree libtest (unstable programmatic API). This is problematic because:build.compiletest-use-stage0-libtest = true
but that's more-or-less a hack / mitigation).compiletest
because we can't easily tailor libtest behavior for rustc/rustdoc/ certain library test suites without regressing all the other libtest consumers.Instead, we can roll our own minimal executor that replaces the libtest executor, which would allow us to drop the dependency on libtest once we migrate over to the new executor.
Known limitations
#![feature(internal_output_capture)]
.Known bugs
Implementation history
compiler/
tree change to inhibitdownload-rustc
Revert compiletest new-executor, to re-land without download-rustc #140233The text was updated successfully, but these errors were encountered: