-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
update miri #52338
update miri #52338
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
and
That's not introduced by this PR, is it? |
cc @kennytm maybe related to all submodules successfully passing CI? 😆 |
@bors r+ p=1 let's see if bors likes this better |
📌 Commit 817c5783b03a6ad17bfa608f3c5c7a800bbd2ddd has been approved by |
⌛ Testing commit 817c5783b03a6ad17bfa608f3c5c7a800bbd2ddd with merge 51d30eef406bc0c6cfd4a175ae23b280927a2c25... |
💔 Test failed - status-appveyor |
A bunch of tests are failing on windows:
|
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
Needs a fix on Windows, which is being developed at rust-lang/miri#401 |
Blocked by #52400 |
#52400 has been merged. |
Yep, now this is blocked on rust-lang/miri#401 :) |
@bors r- #52433 (comment) — miri is broken by #52264. |
All right, miri should be fixed (again). Let's hope nobody else breaks it this time. ;) |
@bors r+ p=1 |
📌 Commit 358b88ca1e8fd72b82aef528032db2e7e06fee99 has been approved by |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
Rebased. @bors r=oli-obk |
@RalfJung: 🔑 Insufficient privileges: Not in reviewers |
@bors r+ |
📌 Commit 9e10b12 has been approved by |
This comment has been minimized.
This comment has been minimized.
cc @alexcrichton -- any idea why @RalfJung doesn't have review privileges, given rust-lang/rust-central-station#72? |
Rollup of 9 pull requests Successful merges: - #52286 (Deny bare trait objects in src/librustc_errors) - #52306 (Reduce the number of clone()s needed in obligation_forest) - #52338 (update miri) - #52385 (Pass edition flags to compiler from rustdoc as expected) - #52392 (AsRef doc wording tweaks) - #52430 (update nomicon) - #52434 (Enable incremental independent of stage) - #52435 (Calculate the exact capacity for 2 HashMaps) - #52446 (Block beta if clippy breaks.) r? @ghost
No description provided.