update Miri

[RalfJung]

r? @ghost

[rustbot]

The Miri subtree was changed

cc @rust-lang/miri

[rustbot]

These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.

If this was unintentional then you should revert the changes before this PR is merged.
Otherwise, you can ignore this comment.

[RalfJung]

@bors r+

[bors]

📌 Commit 9a3cb9e has been approved by RalfJung

It is now in the queue for this repository.

[bors]

⌛ Testing commit 9a3cb9e with merge 6f2e42eb241c024fbe8b31e804d25a13a9c04be2...

[rust-log-analyzer]

The job aarch64-gnu failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[RUSTC-TIMING] tracing_log test:false 3.638
   Compiling rustc_macros v0.1.0 (/checkout/compiler/rustc_macros)
[RUSTC-TIMING] syn test:false 17.070
   Compiling zerofrom-derive v0.1.2
##[error]The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
   Compiling yoke-derive v0.7.1

##[group]Clock drift check
  local time: Tue Aug 22 00:02:00 UTC 2023
  local time: Tue Aug 22 00:02:00 UTC 2023
  network time: Tue, 22 Aug 2023 00:02:00 GMT
##[endgroup]
Session terminated, killing shell...[RUSTC-TIMING] aho_corasick test:false 11.623
 ...killed.
 ...killed.
time="2023-08-22T00:02:02Z" level=error msg="error waiting for container: unexpected EOF"
##[error]The operation was canceled.

[bors]

💔 Test failed - checks-actions

[RalfJung]

@bors retry The runner has received a shutdown signal

[bors]

⌛ Testing commit 9a3cb9e with merge 16349a8d7a7f12844eb5506ba8099ac1e70b541a...

[rust-log-analyzer]

The job armhf-gnu failed! Check out the build log: (web) (plain)

Click to see the possible cause of the failure (guessed by this bot)

failures:

---- [ui] tests/ui/rfcs/rfc-2091-track-caller/caller-location-intrinsic.rs#mir-opt stdout ----

error in revision `mir-opt`: test run failed!
command: RUST_TEST_THREADS="8" "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0-tools-bin/remote-test-client" "run" "0" "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/rfcs/rfc-2091-track-caller/caller-location-intrinsic.mir-opt/a"
--- stdout -------------------------------
--- stdout -------------------------------
uploaded "/checkout/obj/build/x86_64-unknown-linux-gnu/test/ui/rfcs/rfc-2091-track-caller/caller-location-intrinsic.mir-opt/a", waiting for result
--- stderr -------------------------------
thread 'main' panicked at 'client.read_exact(&mut header) failed with Connection reset by peer (os error 104)', src/tools/remote-test-client/src/main.rs:310:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
------------------------------------------

[bors]

💔 Test failed - checks-actions