-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
bump Miri #70897
bump Miri #70897
Conversation
Toolstate fix |
📌 Commit 203accc has been approved by |
🌲 The tree is currently closed for pull requests below priority 1000, this pull request will be tested once the tree is reopened |
@bors p=1001 Let's try again. |
⌛ Testing commit 203accc with merge 48fdfe634e486a5abf20577a18467d5657c6174c... |
💔 Test failed - checks-azure |
@bors retry |
⌛ Testing commit 203accc with merge dc4541ab6869591f8d426525791fa936bb15bf9a... |
💔 Test failed - checks-azure |
@bors p=1 |
@bors retry |
⌛ Testing commit 203accc with merge fe8f44254e8a9872b07e5effc8aa250c6910be6c... |
@bors retry yield |
⌛ Testing commit 203accc with merge 434f470c1d323de31a2890bf960bf2ee99d28bee... |
@bors retry yield |
With all this yielding going on, it looks like we no longer actually prioritize toolstate fixes after all? When can we expect this to land? |
(I yielded this because my rollup spuriously failed; that's always something I do with any rollup. I do not think we should have 3 toolstate fixes in a row overtake rollups.) |
It's more like rollups overtaking toolstate fixes, given the priorities of the underlying PRs. (To be clear, I am not generally opposed to that, but it also never took >48h to land a toolstate fix.) |
⌛ Testing commit 203accc with merge 841e441b0a9755cd346999001021ec4d26a04d9b... |
💔 Test failed - checks-azure |
@bors retry spurious |
⌛ Testing commit 203accc with merge 151b2013e668308bf9950977eb172644f91e7e48... |
bump Miri r? @ghost Cc @rust-lang/miri Fixes rust-lang#70894
@bors retry included in a r0llup |
Thanks. :) |
Rollup of 5 pull requests Successful merges: - rust-lang#70897 (bump Miri) - rust-lang#70900 (Update cargo) - rust-lang#70902 (Update Clippy) - rust-lang#70939 (Add two const generics regression tests) - rust-lang#70958 (Disable try_reserve tests on Android) Failed merges: r? @ghost
Now that rust-lang/miri#940 has been fixed, and has landed in nightly (rust-lang/rust#70897), we should be able to run miri with leak check enabled again!
99: miri: enable leakcheck r=matklad a=RalfJung rust-lang/miri#940 is fixed, so we should be able to enable the leak checker now. :) (However, we'll have to wait until rust-lang/rust#70897 lands so that this is available via rustup.) Co-authored-by: Ralf Jung <post@ralfj.de>
Now that rust-lang/miri#940 has been fixed, and has landed in nightly (rust-lang/rust#70897), we should be able to run miri with leak check enabled again!
r? @ghost Cc @rust-lang/miri
Fixes #70894