[SERVER-53254] increase writeConcern timeout for dropDatabase in tests Created: 07/Dec/20 Updated: 05/Feb/21 Resolved: 05/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Sprint: | Execution Team 2021-01-25, Execution Team 2021-02-08 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 0 | ||||||||||||
| Description |
|
When running dropDatabase in the CI system, since dropDatabase has an internal default of 10 mins when waiting for replicated drops, the writeConcern provided by the tests should contain a timeout that is as long as the default or be left out completely. |