compiletest: pin or restrict supported external dependency versions #128392
Labels
A-compiletest
Area: The compiletest test runner
A-run-make
Area: port run-make Makefiles to rmake.rs
C-cleanup
Category: PRs that clean code up or issues documenting cleanup.
E-hard
Call for participation: Hard difficulty. Experience needed to fix: A lot.
E-needs-design
This issue needs exploration and design to see how and if we can fix/implement it
T-bootstrap
Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
To the best of my knowledge, test suites supported by compiletest currently rely on external dependencies in e.g. ui or run-make test suites but we do not have any sanity checks on their versions or even the specific external dependency used. For example, which C/C++ compilers are picked for a given environment usually calls out to something like the
cc
crate, but we don't otherwise pin them down. This makes reproducing the tests locally very challenging or near impossible. Or for Python, I don't think we sanity check which Python versions are "supported" by the test suites.The text was updated successfully, but these errors were encountered: