fix(couch_replicator): reporting for unexpected test responses
#5007
Conversation
This file contains 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
The freshly introduced debugging statements for tracing the run of the `couch_replicator` scheduler docs tests fail to provide information on unknown errors (possibly crashes) which are coming with a stack trace. Enhance the related case distinction to handle these cases. At the same time, rewrite the assertion on the expected result to make it more specific with regard to the contents of the document.
big-r81
approved these changes
Mar 16, 2024
|
I think I found the reason for the error. This should fix it: #5008 |
|
Thanks @big-r81 nevertheless. |
|
Closing this in favor of #5007. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The freshly introduced debugging statements for tracing the run of the
couch_replicatorscheduler docs tests fail to provide information on unknown errors (possibly crashes) which are coming with a stack trace. Enhance the related case distinction to handle these cases. At the same time, rewrite the assertion on the expected result to make it more specific with regard to the contents of the document.