rust-lang / rust-lang/rust

./x test --help --verbose is not very discoverable and may produce excess output (consider adding --list)

Open
#140,477 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

C-enhancement T-bootstrap
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

Summary

This command lists all the different test targets that exist, however it is not very easy to find this behavior since it is not listed in the normal helptext.

Additionally, this command causes cargo to be run in verbose mode, which causes a lot of usually not interesting info to be printed.

Command used
./x test --help
./x test --help --verbose
Expected behaviour

Somewhere in the regular helptext this functionality is listed, or there is a --list flag that does a similar thing but doesn't run cargo in verbose mode (additionally, a --list flag could accept an argument and only print paths matching that argument).

Actual behaviour

Nothing printed by ./x test --help says how to get a list of test paths.

Bootstrap configuration (bootstrap.toml)
profile = "tools"  # Includes one of the default files in src/bootstrap/defaults
change-id = 138986
Operating system

Arch Linux (rolling)

HEAD

02257c202b33054a623bed712efe7f887b482a02

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 comparing the output of ./x test --help and ./x test --help --verbose, then trace the bootstrap test command's help implementation. Done means the normal help explains how to list test paths, or a --list option provides that behavior without unnecessary verbose Cargo output and optionally filters paths.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.