rust-lang / rust-lang/rust

compiletest: be more robust for cross-compile scenarios with dual under-test toolchains

Open
#160,917 2 comments 0 reactions 1 assignee View on GitHub

@jieyouxu is already working on this.

Since Sep 7, 2026.

A-compiletest C-bug E-hard E-needs-design T-bootstrap T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

compiletest isn't super robust about distinguishing between configuration and environment for the host versus the target-under-test (for cross-compile scenarios). At places, we sometimes don't bother distinguishing the two for "good enough" cases and when host-only testing is the case where we can make things work.

Furthermore, we do not distinguish between the case where you may actually have two "target" toolchains for the purpose of testing wasm proc macros: there is a under-test target toolchain for wasm proc-macros and there's a under-test target toolchain for $other_things

graph TD
    A["host_target(x86_64-unknown-linux-gnu)"] --> B["target_a(wasm32-wasip2)"]
    A --> C["target_b(i686-unknown-linux-gnu)"]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.