-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Spurious clippy CI failure #113585
Comments
Seems same with my PR #113567 (comment) |
@chenyukang your problem was different. the problem Ralf is running into is #113492 (comment). |
The error message and failed test case are both same with my failed CI https://github.com/rust-lang/rust/actions/runs/5526498849/jobs/10081294868 in my new PR #113599 |
gotcha - in that case the rebase probably didn't do anything except rerun ci - this only fails some of the time. https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/CI.20issue.20on.20unrelated.20PRs.3F/near/374468336 has a plausible explanation |
See the discussion at https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/CI.20issue.20on.20unrelated.20PRs.3F/near/374493691. I believe this is an issue with ui_test. |
This is causing lots of problems in CI, so I'm marking it as critical. |
@oli-obk I'll leave it up to you on tracking what needs to be done to revert #113621. It looks like you've been working on it in ui_test, but I'm not involved in clippy development, so I probably shouldn't be the one tracking/fixing things. However, if you have questions on the cargo side, let me know. |
Thanks! After the next clippy sync (tomorrow) this should be fixed. On the ui_test side, the failure is now protected against being spurious and 100% reproducible. I'll ship that to miri soon to prevent the same thing from happening there. |
In #113569, clippy CI failed, and I don't think that can be caused by my PR:
Cc @rust-lang/clippy
The text was updated successfully, but these errors were encountered: