chore: add debugging for failing test case, see COUCHDB-3413#518
Merged
Conversation
Contributor
|
+1 At first I was about to mention that EUnit captures and hides all the stdout output but then noticed we send output directly to console with |
Member
Author
|
re |
Contributor
|
Alright, let's go with |
nickva
pushed a commit
to nickva/couchdb
that referenced
this pull request
Sep 7, 2022
The example result for _all_docs/queries did not match the example request and it was incorrect in a sense that the values `id` fields were not matching the respective values of `key` fields and there was a document returned that was not specified in the query. This change fixes the issue described above by editing the ids so that they match the keys now and removing the element that was not specified in the request.
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
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.
Overview
Add test case to see what trips up this test case in COUCHDB 3413.
I assume it is one where the cluster returns a 500 error.
Testing recommendations
This needs to run in CI for a bit until it pops up again.
JIRA issue number
https://issues.apache.org/jira/browse/COUCHDB-3413
Checklist
with the correct commit hash once this PR get merged.