Skip to content

We should document what external dependencies we assume for our test suites #125585

Open
@jieyouxu

Description

@jieyouxu

Location

The test suites, especially tests/run-make and tests/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):

  • Utilities: e.g. nm, grep.
  • C/C++ compilers, e.g. what cc points to is a massive pain.
  • Python: again, which python version is also a massive pain.
  • Make and makefiles: we're trying to escape from this
  • Shell: bash? or what do the various bash scripts assume?

For example, the run-make test suite has a bunch of assumed external dependencies (like nm) which are not documented AFAICT.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-compiletestArea: The compiletest test runnerA-docsArea: Documentation for any part of the project, including the compiler, standard library, and toolsA-testsuiteArea: The testsuite used to check the correctness of rustcC-cleanupCategory: PRs that clean code up or issues documenting cleanup.E-help-wantedCall for participation: Help is requested to fix this issue.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions