diff options
| author | bors <bors@rust-lang.org> | 2019-09-20 11:38:56 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2019-09-20 11:38:56 +0000 |
| commit | 9ad1e7c46cf690b7ec6953b142430d21ca2d8799 (patch) | |
| tree | d46ba9ea92d542462d5f01cb38ca0b244ae8a564 /src/libsyntax/parse/parser/generics.rs | |
| parent | 72252646a8f781509e6756180182887653f657ee (diff) | |
| parent | 72ea960056d40f1fcb5efb42d5914b35f908f63e (diff) | |
| download | rust-9ad1e7c46cf690b7ec6953b142430d21ca2d8799.tar.gz rust-9ad1e7c46cf690b7ec6953b142430d21ca2d8799.zip | |
Auto merge of #64553 - alexcrichton:windows-bash-install-scripts, r=Mark-Simulacrum
azure: Convert Windows installations scripts to `bash` Looks like `script`, which uses `cmd.exe`, doesn't have fail-fast behavior and if a leading command fails the script doesn't actually fail so long as the last command succeeds. We instead want the opposite behavior where if any step fails the whole script fails. I don't really know `cmd.exe` that well, nor powershell, so I've opted to move everything to `bash` which should be a good common denominator amongst all platforms to work with. Additionally I know that `set -e` works to cause scripts to fail fast. Closes #64551
Diffstat (limited to 'src/libsyntax/parse/parser/generics.rs')
0 files changed, 0 insertions, 0 deletions