Closed
Conversation
michaelsproul
added
do-not-merge
dependencies
Member
Author
|
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. |
Member
Author
|
Ding ding ding! We have a failure. Trying batch 2A:
|
Member
Author
|
Batch 2A failed, so narrowing down to batch 3A:
|
Member
Author
|
Ok, the regression is definitely caused by some change in |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Trying to find which of the dependency updates break CI. See: