rust-lang / rust-lang/rust

Tracking issue for migrating from Glacier to compiletest ICE/crash tracking

Open
#125,459 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-compiletest A-testsuite C-tracking-issue S-tracking-impl-incomplete T-compiler
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Tracks the necessary steps to "fully"[^1] transition from rust-lang/glacier to compiletest ICE/crash tracking inside tests/crashes/.
See also this Zulip topic.

Steps
Unresolved Questions
  • Should we implement rustdoc support via subdirectories/tests suites (e.g., tests/crashes/rustdoc/) or via a new compiletest directive (e.g., //@ bin: rustdoc)
    • If we do the former, should we move rustc tests from tests/crashes/ to tests/crashes/rustc/?
  • Should we define precise procedures for adding new tests to tests/crashes?

[^1]: Glacier|_{rust-lang/rust}, i.e., restriction of Glacier to rust-lang/rust (excluding git submodules/subtrees), i.e., Glacier without support for rustfmt, Cargo, Clippy, Miri ICE/crash tracking

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.

Research direction

Start by reviewing the remaining checklist items for tests/crashes/, especially rustdoc ICE/crash tracking, run-make/rmake support, and the Rust Forge issue-triaging chapter. Resolve the documented questions about rustdoc subdirectories versus a compiletest directive and procedures for adding tests. Done means the remaining migration steps are completed or explicitly decided.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.