-
Notifications
You must be signed in to change notification settings - Fork 549
Open
Labels
A-compiletestArea: src/tools/compiletestArea: src/tools/compiletestA-test-suiteArea: rust-lang/rust test suitesArea: rust-lang/rust test suitesE-hardDifficulty: might require advanced knowledgeDifficulty: might require advanced knowledgeI-terseIssue: info is very terseIssue: info is very terseT-bootstrapRelevant to bootstrap teamRelevant to bootstrap teamT-compilerRelevant to compiler teamRelevant to compiler team
Description
https://rustc-dev-guide.rust-lang.org/tests/running.html#running-tests-manually explains how to run the tests manually. However, it does not explain how to do this for check-pass and build-pass tests. I assume for build-pass it might just be a regular rustc invocation, but how do I check-pass tests by hand? That would be quite good to know when evaluating whether check-pass is sufficient to reproduce a problem.
Metadata
Metadata
Assignees
Labels
A-compiletestArea: src/tools/compiletestArea: src/tools/compiletestA-test-suiteArea: rust-lang/rust test suitesArea: rust-lang/rust test suitesE-hardDifficulty: might require advanced knowledgeDifficulty: might require advanced knowledgeI-terseIssue: info is very terseIssue: info is very terseT-bootstrapRelevant to bootstrap teamRelevant to bootstrap teamT-compilerRelevant to compiler teamRelevant to compiler team