-
Notifications
You must be signed in to change notification settings - Fork 386
cargo miri test
stopped working for doc tests
#4323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Yeah our CI also turned all red this morning.^^ Something must have changed in rustdoc. Strange that rustc CI did not catch this... |
This is almost certainly caused by rust-lang/rust#141093. |
Merged
I was wondering why rustc CI didn't catch this... the answer is that that uses bootstrap cargo which doesn't have that PR so things still work fine there. |
github-merge-queue bot
pushed a commit
to bevyengine/bevy
that referenced
this issue
May 17, 2025
# Objective The required miri check is currently failing due to rust-lang/miri#4323 Let's pin nightly to yesterday to not be blocked today. ## Solution - Pinned nightly to `nightly-2025-05-16` ## Testing - Let's see if the pipeline is green on this PR :D
BenjaminBrienen
pushed a commit
to BenjaminBrienen/bevy
that referenced
this issue
May 17, 2025
# Objective The required miri check is currently failing due to rust-lang/miri#4323 Let's pin nightly to yesterday to not be blocked today. ## Solution - Pinned nightly to `nightly-2025-05-16` ## Testing - Let's see if the pipeline is green on this PR :D
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since a recent nightly release
cargo miri test
errors if it is not run with the--lib
flag.To reproduce:
Output:
Versions:
Here is an demo repo that fails ci:
https://github.com/bluurryy/cargo-miri-bug
https://github.com/bluurryy/cargo-miri-bug/actions/runs/15080920895/job/42397281329
The text was updated successfully, but these errors were encountered: