rust-lang / rust-lang/rust

It is unclear how to reproduce "Testing stage2 error-index (x86_64-unknown-linux-gnu)"

Open
#132,725 3 comments 0 reactions 1 assignee View on GitHub

@onur-ozkan is already working on this.

Since May 1, 2025.

A-contributor-roadblock A-diagnostics C-bug T-bootstrap
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

In this CI run, I got the following error:


Testing stage2 error-index (x86_64-unknown-linux-gnu)
STDOUT:

running 1106 tests
[...]

failures:
    /checkout/obj/build/x86_64-unknown-linux-gnu/test/error-index.md - Rust_Compiler_Error_Index::E0094 (line 1995)
    /checkout/obj/build/x86_64-unknown-linux-gnu/test/error-index.md - Rust_Compiler_Error_Index::E0211::_::Note__this_error_code_is_no_longer_emitted_by_the_compiler_ (line 3999)

test result: FAILED. 1043 passed; 2 failed; 61 ignored; 0 measured; 0 filtered out; finished in 8.56s


Command CFG_RELEASE_CHANNEL="nightly" RUSTC_BOOTSTRAP="1" RUSTC_STAGE="2" RUSTC_SYSROOT="/checkout/obj/build/x86_64-unknown-linux-gnu/stage2" RUSTDOC_LIBDIR="/checkout/obj/build/x86_64-unknown-linux-gnu/stage2/lib" RUSTDOC_REAL="/checkout/obj/build/x86_64-unknown-linux-gnu/stage2/bin/rustdoc" RUST_TEST_THREADS="16" "/checkout/obj/build/bootstrap/debug/rustdoc" "-Wrustdoc::invalid_codeblock_attributes" "-Dwarnings" "-Znormalize-docs" "-Z" "unstable-options" "--test" "/checkout/obj/build/x86_64-unknown-linux-gnu/test/error-index.md" "--test-args" "" (failure_mode=DelayFail) has failed. Rerun with -v to see more details.
Build completed unsuccessfully in 0:41:18

I have no idea how to reproduce this locally. "Testing stage2 error-index" sounds like it should be ./x test error-index, but that does not work. So right now I am making guesses and pushing that to the PR, leading to a 40min round-trip time for an edit-compile cycle...

In general, when an x.py job fails, it'd be really nice if it could, at the end of the error log, give some idea of how this can be reproduced -- for instance, it can also be non-trivial to find out which target the failing test ran on.

Cc @rust-lang/bootstrap

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.