compiletest: more granular `--nocapture` for `run-make` tests
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Would it be possible to add a way to revert back to the old behavior? For cg_clif this makes testing the rustc test suite very verbose. I have to use
--nocaptureto see any test failures in the first place aspanic=abortmeans that without it compiletest aborts before it gets a chance to print the test failures, but I would like to not have my terminal getting spammed with the output of all passing tests.
Originally posted by @bjorn3 in https://github.com/rust-lang/rust/issues/134111#issuecomment-2554625017
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating compiletest's handling of --nocapture and the run-make test output path. Compare the current behavior with the old behavior described here, focusing on how passing and failing tests are printed when panic=abort is used. Done means run-make failures remain visible without printing output from every passing test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100