Thank you for contributing to Miri!
Please remember to not force-push to the PR branch except when you need to rebase due to a conflict or when the reviewer asks you for it.

Reminder, once the PR becomes ready for a review, use @rustbot ready.

This failure is weird, the mutex_poison.rs test passes on my machine with the expected output, but not in CI?
Maybe something changed in the upstream implementation of one of the functions used in the test, so a rebase could potentially fix this?

You probably need to rebase over #4617 yeah.

This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.

Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.

The rebase fixed the previous CI failure, but there is another one now, possibly spurious? Nothing in this PR should affect Windows, or Linux on Arm specifically.

Yeah those are just network timeouts, you can ignore them.

This looks great, thanks! Please squash the commits using ./miri squash. Then write @rustbot ready after you force-pushed the squashed PR.

@rustbot author

@rustbot ready