Open
Description
openedon May 26, 2024
Location
bootstrap <-> compiletest <-> testsuites
Summary
In tests/run-make
(for example, but the lack of docs isn't limited to this particular test suite) we assume a bunch of env vars being available, but AFAIK there isn't any docs on which env vars are assumed available between the bootstrap -> compiletest -> test suites pipeline and for what reasons. It'd be nice to have any kind of docs on them.
The current state is that:
- bootstrap sets up a bunch of env vars, which are made available to compiletest
- compiletest assumes bootstrap-set env vars are available
- compiletest sets up a bunch of env vars, often conditionally available to specific test suites
- tests inside test suites assume compiletest-set env vars are available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
Area: The compiletest test runnerArea: documentation for any part of the project, including the compiler, standard library, and toolsArea: The testsuite used to check the correctness of rustcCategory: PRs that clean code up or issues documenting cleanup.Call for participation: Medium difficulty. Experience needed to fix: Intermediate.Call for participation: An issue involves lots of work and is better handled as many small tasks.Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)Relevant to the compiler team, which will review and decide on the PR/issue.
Type
Projects
Status
Backlog