Updating collections.json#393
Merged
Merged
Conversation
Signed-off-by: Chathurangi Shyalika <chathurangishyalika@daniels-mbp.watson.ibm.com>
DhavalRepo18
approved these changes
Jun 19, 2026
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
2 participants
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.
Summary
Updates CouchDB collection naming so scenario-suite manifests load the failure-code CSV correctly.
Changes
src/couchdb/collections.jsonWhy
Scenario-suite execution failed because the manifest key and CouchDB collection config did not match. The loader treated the failure-code file with the wrong parser and crashed during initialization.
Result
Scenario 301 now loads correctly, and benchmark batch runs can reset and reload CouchDB without hitting the CSV/JSON parsing mismatch.
Testing
couchdb.init_data.pyfor scenario 301failure_code.csvis loaded successfully