-
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
Rollup of 5 pull requests #71978
Rollup of 5 pull requests #71978
Conversation
…trochenkov reword "possible candidate" import suggestion This suggestion has always read a bit awkwardly to me, particularly the "possible better candidate" variant. This commit rewords the suggestion to be more concise and mention the kind of the suggested item. There isn't a nice way to label individual suggestions, so I opted to use "items" in the case of multiple suggestions.
Add some regression tests Closes rust-lang#29988 Closes rust-lang#34979 Pick up two snippets that have been fixed from rust-lang#67945 (shouldn't be closed yet!)
…acrum tests: Fix warnings in `rust_test_helpers.c` MSVC is silly and doesn't recognize `assert` as diverging.
Grammar I've split this into individual changes so that people can veto individually. I'm not attached to most of them. `zeroes` vs. `zeros` is why I took the effort to run this through app.grammarly (which disappointingly didn't even notice).
…, r=oli-obk use hex for pointers in Miri error messages Also refine vtable error message: distinguish between "drop fn does not point to a function" and "drop fn points to a function with the wrong signature".
@bors r+ rollup=never p=5 |
📌 Commit 1f73d8d has been approved by |
⌛ Testing commit 1f73d8d with merge b7d2d2caa3cd019770b06e24920f20126db10cdb... |
💔 Test failed - checks-actions |
@bors retry |
⌛ Testing commit 1f73d8d with merge 9a32b4ad89ea74677eaa678f7580394d59c75bd6... |
The log says
That codegen test was added in #71952. |
However @pietroalbini something is wrong with whatever bors linked to above, both here and in #71966: it linked to https://github.com/rust-lang-ci/rust/runs/653177525 which just says "mark the job as a failure",
One has to ignore that and find the actual failing job in the list on the left to figure out what happened. |
Yeh i got a different thing (maybe a different build) hence assumed spurious. I'll r- that one and re-roll |
💔 Test failed - checks-actions |
Successful merges:
rust_test_helpers.c
#71959 (tests: Fix warnings inrust_test_helpers.c
)Failed merges:
r? @ghost