Auto merge of #867 - RalfJung:readme, r=RalfJung
README: move CI remark down to CI section
This commit is contained in:
commit
0347e1bd69
2 changed files with 5 additions and 4 deletions
|
|
@ -18,7 +18,7 @@ cache:
|
|||
|
||||
install:
|
||||
# Install Rust
|
||||
- curl -sSf -o rustup-init.exe https://win.rustup.rs/
|
||||
- curl -sSf --retry 3 -o rustup-init.exe https://win.rustup.rs/
|
||||
- rustup-init.exe -y --default-host %TARGET% --default-toolchain stable
|
||||
- set PATH=%USERPROFILE%\.cargo\bin;%PATH%
|
||||
# Install "master" toolchain
|
||||
|
|
|
|||
|
|
@ -73,9 +73,7 @@ Now you can run your project in Miri:
|
|||
3. If you have a binary project, you can run it through Miri using `cargo miri run`.
|
||||
|
||||
The first time you run Miri, it will perform some extra setup and install some
|
||||
dependencies. It will ask you for confirmation before installing anything. If
|
||||
you run Miri on CI, run `cargo miri setup` to avoid getting interactive
|
||||
questions.
|
||||
dependencies. It will ask you for confirmation before installing anything.
|
||||
|
||||
You can pass arguments to Miri after the first `--`, and pass arguments to the
|
||||
interpreted program or test suite after the second `--`. For example, `cargo
|
||||
|
|
@ -115,6 +113,9 @@ cargo miri setup
|
|||
cargo miri test -- -- -Zunstable-options --exclude-should-panic
|
||||
```
|
||||
|
||||
We use `cargo miri setup` to avoid getting interactive questions about the extra
|
||||
setup needed for Miri.
|
||||
|
||||
### Common Problems
|
||||
|
||||
When using the above instructions, you may encounter a number of confusing compiler
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue