compiletest: inconsistent and inconvenient ways to request verbose test output
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
compiletest has some strange --nocapture (which is a libtest thing) support for ui tests but inconsistently for other test suites. crashes test suite uses an env var COMPILETEST_VERBOSE_CRASHES=1 to unhide the crashes test failure output. run-make test suite has multiple layer of hiding going on.
There's also the bootstrap verbose/verbose tests -> compiletest handling.
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 tracing compiletest's handling of verbose output across the ui, crashes, and run-make test suites, including the COMPILETEST_VERBOSE_CRASHES=1 path. Then inspect the bootstrap verbose/verbose-tests handoff to compiletest. Done means the issue's inconsistent output controls and layered hiding have a clearly defined, consistent request mechanism.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100