You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would appear that the Miri cron job build failed. Would you mind investigating this issue?
177
+
It would appear that the [Miri cron job build]('"https://github.com/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID"') failed.
178
+
179
+
This likely means that rustc changed the miri directory and
180
+
we now need to do a [`./miri rustc-pull`](https://github.com/rust-lang/miri/blob/master/CONTRIBUTING.md#importing-changes-from-the-rustc-repo).
Copy file name to clipboardexpand all lines: src/tools/miri/tests/fail/terminate-terminator.stderr
+3-1
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,5 @@
1
+
warning: You have explicitly enabled MIR optimizations, overriding Miri's default which is to completely disable them. Any optimizations may hide UB that Miri would otherwise detect, and it is not necessarily possible to predict what kind of UB will be missed. If you are enabling optimizations to make Miri run faster, we advise using cfg(miri) to shrink your workload instead. The performance benefit of enabling MIR optimizations is usually marginal at best.
2
+
1
3
thread 'main' panicked at 'explicit panic', $DIR/terminate-terminator.rs:LL:CC
2
4
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
3
5
error: abnormal termination: panic in a function that cannot unwind
@@ -23,5 +25,5 @@ LL | panic_abort();
23
25
24
26
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
25
27
26
-
error: aborting due to previous error
28
+
error: aborting due to previous error; 1 warning emitted
0 commit comments