diff options
| author | Mazdak Farrokhzad <twingoow@gmail.com> | 2019-06-29 11:18:07 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2019-06-29 11:18:07 +0200 |
| commit | 0721364f0de6191cddeaaaeb112fb74aa1a9e30a (patch) | |
| tree | 97d7e70fbfd8a91d0f13e1d35241283112684621 /src/test/ui/thinlto | |
| parent | 6c0ab739fb77c67d00ba5b5fa357deec404f9bce (diff) | |
| parent | 93077f3f3922817a70013c403831bf1db4a30114 (diff) | |
| download | rust-0721364f0de6191cddeaaaeb112fb74aa1a9e30a.tar.gz rust-0721364f0de6191cddeaaaeb112fb74aa1a9e30a.zip | |
Rollup merge of #61755 - Centril:compiletest-force-check, r=petrochenkov
Add `--pass $mode` to compiletest through `./x.py`
Adds a flag `--pass $mode` to compiletest, which is exposed through `./x.py`.
When `--pass $mode` is passed, `{check,build,compile,run}-pass` tests will be forced to run under the given `$mode` unless the directive `// ignore-pass` exists in the test file.
The modes are explained in https://github.com/rust-lang/rust/pull/61778:
- `check` has the same effect as `cargo check`
- `build` or `compile` have the same effect as `cargo build`
- `run` has the same effect as `cargo run`
On my machine, `./x.py -i test src/test/run-pass --stage 1 --pass check` takes 38 seconds whereas it takes 2 min 7 seconds without `--pass check`.
cc https://github.com/rust-lang/rust/issues/61712
r? @petrochenkov
Diffstat (limited to 'src/test/ui/thinlto')
0 files changed, 0 insertions, 0 deletions