diff options
| author | bors <bors@rust-lang.org> | 2023-10-22 02:00:29 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-10-22 02:00:29 +0000 |
| commit | 9e3f784eb2c7c847b6c3578b373c0e0bc9233ca3 (patch) | |
| tree | d350d50cd27c375d3c2836b4621c49e135da8767 /compiler/rustc_codegen_llvm/src/coverageinfo/mod.rs | |
| parent | 97a28940626caf771d332525315079ded8a36e47 (diff) | |
| parent | c2524bc6899a1a7feebda032dd26f751504e94e5 (diff) | |
| download | rust-9e3f784eb2c7c847b6c3578b373c0e0bc9233ca3.tar.gz rust-9e3f784eb2c7c847b6c3578b373c0e0bc9233ca3.zip | |
Auto merge of #116932 - Kobzol:fix-stage1-tests, r=Mark-Simulacrum
Fix x86_64-gnu-llvm-15 CI tests The CI script was broken - if there was a test failure in the first command chain (inside the `if`), CI would not report the failure. It happened because there were two command chains separated by `&&` in the script, and since `set -e` doesn't exit for chained commands, if the first chain has failed, the script would happily continue forward, ignoring any test failures. This could be fixed e.g. by adding some `|| exit 1` to the first chain, but I suppose that the `&&` chaining is unnecessary here anyway. Reported [on Zulip](https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/test.20failure.20didn't.20stop.20CI). Fixes: https://github.com/rust-lang/rust/issues/116867
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/coverageinfo/mod.rs')
0 files changed, 0 insertions, 0 deletions