9e3f784eb2
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 |
||
|---|---|---|
| .. | ||
| bad_opt_access.rs | ||
| bad_opt_access.stderr | ||
| default_hash_types.rs | ||
| default_hash_types.stderr | ||
| diagnostics.ftl | ||
| diagnostics.rs | ||
| diagnostics.stderr | ||
| lint_pass_impl_without_macro.rs | ||
| lint_pass_impl_without_macro.stderr | ||
| qualified_ty_ty_ctxt.rs | ||
| qualified_ty_ty_ctxt.stderr | ||
| query_stability.rs | ||
| query_stability.stderr | ||
| rustc_pass_by_value.rs | ||
| rustc_pass_by_value.stderr | ||
| span_use_eq_ctxt.rs | ||
| span_use_eq_ctxt.stderr | ||
| ty_tykind_usage.rs | ||
| ty_tykind_usage.stderr | ||