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:
parent
08162cbd1e
commit
30ca044a71
1 changed files with 3 additions and 3 deletions
|
|
@ -68,19 +68,19 @@ Likewise, you can test a single file by passing its path:
|
|||
### Run tests on the standard library
|
||||
|
||||
```bash
|
||||
./x.py test library/std
|
||||
./x.py test --stage 0 library/std
|
||||
```
|
||||
|
||||
### Run the tidy script and tests on the standard library
|
||||
|
||||
```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
|
||||
|
||||
```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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue