-
Notifications
You must be signed in to change notification settings - Fork 958
Cargo update bisect #6607
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
Cargo update bisect #6607
Conversation
|
First batch is my best guess of crates that might be breaking:
If this first batch fails we can split these crates into two groups and see which side the failure lies on. If this batch succeeds we know the failure is in one of the other cargo updates. |
|
Ding ding ding! We have a failure. Trying batch 2A:
|
|
Batch 2A failed, so narrowing down to batch 3A:
|
|
Ok, the regression is definitely caused by some change in |
Proposed Changes
Trying to find which of the dependency updates break CI. See: