-
Notifications
You must be signed in to change notification settings - Fork 13k
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
[Question] Miri is in "test pass" state but not available in latest nightly #79129
Comments
Oh, I had not even noticed this, thanks! This looks like a rustc issue, so I'll move the issue there. |
Cc @rust-lang/infra any idea why Miri is missing from |
The log at https://github.com/rust-lang-ci/rust/runs/1410170664 looks good in terms of tests, but one thing is strange:
Notice the "test-fail" for "cargo-miri". However, I don't think anything actually cares about that test state, so I am not sure if this is actually a problem. I guess something is going wrong when doing the nightly release (Miri has special logic there to avoid shipping when tests fail), but I do not know how to access the logs for that. |
Thanks for the report! This is a bug in our release process: rust-lang/promote-release#30
Release process logs are not available publicly unfortunately :( |
rust-lang/promote-release#30 has been closed, but Miri is still not available due to #79176. Maybe Miri will be available tomorrow and this can be closed then. |
Miri is in "test pass" state in https://rust-lang-nursery.github.io/rust-toolstate/ since #78990 and #78937 has been closed. Also I didn't found any new issue from
@rust-highfive
about Miri inrust-lang/rust
, so I assume Miri should build from themaster
branch of it.However, Miri is not available in the latest nightly (
nightly-2020-11-17
, f5230fb) fromrustup
. f5230fb already contains #78990. Actually Miri is missing sincenightly-2020-11-10
, and is still missing even #78990 has been merged.I can't find any additional information about Miri in the latest nightly. What's going on with it?
Edit: I mentioned the wrong PR. It should be #78990 instead of
#78890
.The text was updated successfully, but these errors were encountered: