@@ -212,12 +212,13 @@ Some common invocations of `x.py` are:
212212 & everything builds in the correct manner.
213213- ` x.py test src/libstd --stage 1 ` - test the standard library without
214214 recompiling stage 2.
215- - ` x.py test src/test/run-pass --filter TESTNAME ` - Run a matching set of tests.
215+ - ` x.py test src/test/run-pass --test-args TESTNAME ` - Run a matching set of
216+ tests.
216217 - ` TESTNAME ` should be a substring of the tests to match against e.g. it could
217218 be the fully qualified test name, or just a part of it.
218219 ` TESTNAME=collections::hash::map::test_map::test_capacity_not_less_than_len `
219220 or ` TESTNAME=test_capacity_not_less_than_len ` .
220- - ` x.py test src/test/run-pass --stage 1 --filter <substring-of-test-name> ` -
221+ - ` x.py test src/test/run-pass --stage 1 --test-args <substring-of-test-name> ` -
221222 Run a single rpass test with the stage1 compiler (this will be quicker than
222223 running the command above as we only build the stage1 compiler, not the entire
223224 thing). You can also leave off the directory argument to run all stage1 test
@@ -284,7 +285,7 @@ been approved. The PR then enters the [merge queue][merge-queue], where @bors
284285will run all the tests on every platform we support. If it all works out,
285286@bors will merge your code into ` master ` and close the pull request.
286287
287- [ merge-queue ] : http ://buildbot.rust-lang.org/homu/queue/rust
288+ [ merge-queue ] : https ://buildbot.rust-lang.org/homu/queue/rust
288289
289290Speaking of tests, Rust has a comprehensive test suite. More information about
290291it can be found
403404[ tlgba ] : http://tomlee.co/2014/04/a-more-detailed-tour-of-the-rust-compiler/
404405[ ro ] : http://www.rustaceans.org/
405406[ rctd ] : ./COMPILER_TESTS.md
406- [ cheatsheet ] : http ://buildbot.rust-lang.org/homu/
407+ [ cheatsheet ] : https ://buildbot.rust-lang.org/homu/
0 commit comments