We should document what external dependencies we assume for our test suites #125585
Labels
A-compiletest
Area: The compiletest test runner
A-docs
Area: Documentation for any part of the project, including the compiler, standard library, and tools
A-testsuite
Area: The testsuite used to check the correctness of rustc
C-cleanup
Category: PRs that clean code up or issues documenting cleanup.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Location
The test suites, especially
tests/run-make
andtests/run-make-fulldeps
.Summary
It'd be nice for people to be able to reliably run test suites without necessarily having to rely on Docker environments, or at least know what external dependencies are assumed to be available (and what version/flavor as well) by the test suites. This is also relevant for people trying to work on or maintain new targets if they want to run the test suites. Example dependencies (non-exhaustive, have not fully surveyed):
nm
,grep
.cc
points to is a massive pain.bash
? or what do the various bash scripts assume?For example, the
run-make
test suite has a bunch of assumed external dependencies (likenm
) which are not documented AFAICT.The text was updated successfully, but these errors were encountered: