compiletest: inconsistent and inconvenient ways to request verbose test output #134110
Open
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.
Metadata
Assignees
Labels
Area: The compiletest test runnerArea: test infrastructure (may span bootstrap/compiletest/more)Area: The testsuite used to check the correctness of rustcCategory: This is a bug.Call for participation: Hard difficulty. Experience needed to fix: A lot.Call for partcipation: This issues needs some investigation to determine current statusRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
Type
Projects
Status
Backlog
Activity