[GODRIVER-234] Specify write concern in listDatabases test to fix failures on sharded clusters Created: 13/Feb/18  Updated: 28/Oct/23  Resolved: 13/Feb/18

Status: Closed
Project: Go Driver
Component/s: None
Affects Version/s: 0.0.1
Fix Version/s: 0.0.1

Type: Task Priority: Major - P3
Reporter: Samuel Rossi (Inactive) Assignee: Samuel Rossi (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

The listDatabases test inserts a number of documents and then checks that the database they were inserted into exists. This test fails occasionally when run against a sharded cluster due to the default write concern being used. We should specify a write concern to fix this.



 Comments   
Comment by Samuel Rossi (Inactive) [ 13/Feb/18 ]

Code review url: https://review.gerrithub.io/#/c/399746/

Comment by Githook User [ 13/Feb/18 ]

Author:

{'email': 'saghmrossi@gmail.com', 'name': 'Saghm Rossi', 'username': 'saghm'}

Message: GODRIVER-234 Specify write concern in listDatabases test to fix failures on sharded clusters

Change-Id: I14173c603a9bd7a04ed64b266d3108ffaa945851
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/a2de2b10d6d45a2a78f40e1746833dcba1aa60cc

Generated at Thu Feb 08 08:33:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.