-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Update Clippy #59617
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 Clippy #59617
Conversation
|
@bors r+ p=2 make sure this doesn't need a lockfile update to build |
📌 Commit 7c0db1435438207e670aae34f73ddf69a52d91e7 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 |
Yeah it needed a Cargo.lock update (Deps update in Clippy). Sorry forgot about that. |
@bors r+ |
📌 Commit 718e84912c551229961ba867801e8c965823c986 has been approved by |
⌛ Testing commit 718e84912c551229961ba867801e8c965823c986 with merge dd230b9f74ce398212b329af637d56d71b770dd4... |
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 |
💔 Test failed - checks-travis |
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
|
Can I do something about the |
I have no idea what's going on there. |
@gnzlbg , any idea? |
We have been slowly fixing linkage / tools issues in #59440 , and now all ui tests pass, ui-fulldeps is still failing. cc @alexcrichton |
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 |
Sorry I do not have time to keep up with all what's going on around libtest/clippy. I have no idea why it broke in the first place or what may be needed to fix it. If this is too much of a problem we may just need to revert the extraction of libtest. I just don't have time to always be on call to debug all issues related to this right now. |
@alexcrichton I think the correct fix is blocked on your review at rust-lang/libtest#11 and #59440 . We're not asking you to debug things, but please review the PRs that are out there. What's going on is that an incomplete libtest update landed, and the fix for that has not merged in weeks, and we've had to resort to some unsafe trickery to work around that. We were told the fix would land pretty quickly, but it hasn't, and in the meantime more breakages piled up. We do plan to revert everything next week if it's not fixed yet. |
#59440 still fails the tests. |
@Manishearth I don't really know why I'm the one this is all getting pinned on. I have already effectively approved those PRs and they're just trying to get to the point where they can actually land, they're both works in progress. I had basically nothing to do with extracting libtest other than helping out on some guidance of how to organize it. I furthermore have basically no knowledge how any of this is tied to clippy. I realize that I'm connected tangentially to a lot of things, but I really don't have the time any more to get pulled into and cc'd on everything related to anything I used to work on. |
I'm not pinning this on you, this is a bit of a multi-way disaster, I'm
saying that part of this was the libtest PR being blocked on your review.
…On Wed, Apr 3, 2019, 11:14 AM Alex Crichton ***@***.***> wrote:
@Manishearth <https://github.com/Manishearth> I don't really know why I'm
the one this is all getting pinned on. I have already effectively approved
those PRs and they're just trying to get to the point where they can
actually land, they're both works in progress. I had basically nothing to
do with extracting libtest other than helping out on some guidance of how
to organize it. I furthermore have basically no knowledge how any of this
is tied to clippy.
I realize that I'm connected tangentially to a lot of things, but I really
don't have the time any more to get pulled into and cc'd on everything
related to anything I used to work on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59617 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABivSB_ECFs_EHaqn4maMmVT8PZrIZ6Jks5vdO-hgaJpZM4cWkk8>
.
|
To be clear, I don't quite know what the libtest situation is, however to me it seemed like @gnzlbg was blocked on you and has been for a while. |
We can fix compiletest-rs on crates.io without landing any of those PRs. Is that the only thing that needs fixing @Manishearth or are there other issues ? |
I'm not sure at this point, this took so long that a lot of things piled up.
I _think_ that should be fine, but I don't know how to fix compiletest
here. If you can do that and update clippy for that, we can see if it works
again.
…On Wed, Apr 3, 2019, 11:23 AM gnzlbg ***@***.***> wrote:
We can fix compiletest-rs on crates.io without landing any of those PRs.
Is that the only thing that needs fixing @Manishearth
<https://github.com/Manishearth> or are there other issues ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#59617 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABivSNhnWCnL4kaIZjkxve8tYUHiVQAnks5vdPGhgaJpZM4cWkk8>
.
|
This is superseded by #59783 |
cc rust-lang/rust-clippy#3905
cc rust-lang/rust-clippy#3913
cc #59396
This should make Clippy appear to be test-pass. This introduces 3 Bugs to Clippy, which are tracked.
r? @Manishearth @oli-obk