[SERVER-20818] Add wtimeouts to writeConcerns in sharding suite tests Created: 08/Oct/15 Updated: 06/Dec/22 Resolved: 06/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding
|
||||||||
| Sprint: | Sharding 10 (02/19/16), Sharding 16 (06/24/16), Sharding 17 (07/15/16), Sharding 18 (08/05/16), Sharding 2016-08-29, Sharding 2016-09-19, Sharding 2016-10-10 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently there are 8 jstests that make use of writeConcern without supplying a wtimeout. In order to ensure tests fail in a timely manner and give helpful Javascript error messages, we should add reasonable wtimeouts to all of them. |