From 7609eb11eee3915d89ca0ae7513ad88b96f82788 Mon Sep 17 00:00:00 2001 From: Joshua Nelson Date: Wed, 23 Sep 2020 11:46:43 -0400 Subject: [PATCH] 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/. --- src/tests/running.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/tests/running.md b/src/tests/running.md index 1043f87a..5e18b8a9 100644 --- a/src/tests/running.md +++ b/src/tests/running.md @@ -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