mirror
/
rustc-dev-guide
mirror of https://github.com/rust-lang/rustc-dev-guide.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Don't recommend building the compiler for running tests on the standard library (#887) 

Thought of this while reading https://internals.rust-lang.org/t/contributing-changes-to-std/12829/.
This commit is contained in:
Joshua Nelson 2020-09-23 11:46:43 -04:00 committed by GitHub
parent 2a09b06365
commit 22b096ba2f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/tests/running.md
View File

@ -68,19 +68,19 @@ Likewise, you can test a single file by passing its path:
### Run tests on the standard library ### Run tests on the standard library
```bash ```bash
./x.py test library/std ./x.py test --stage 0 library/std
``` ```
### Run the tidy script and tests on the standard library ### Run the tidy script and tests on the standard library
```bash ```bash
./x.py test tidy library/std ./x.py test --stage 0 tidy library/std
``` ```
### Run tests on the standard library using a stage 1 compiler ### Run tests on the standard library using a stage 1 compiler
```bash ```bash
> ./x.py test library/std ./x.py test library/std
``` ```
By listing which test suites you want to run you avoid having to run By listing which test suites you want to run you avoid having to run