[SERVER-72184] Use assert.soon for isConfigCommitted in reconfig tests Created: 16/Dec/22 Updated: 29/Oct/23 Resolved: 19/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Huayu Ouyang | Assignee: | Huayu Ouyang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 13 | ||||||||||||
| Description |
|
assert(isConfigCommitted) is failing in some reconfig tests because the oplog commitment portion is not satisfied yet. We should change this to an assert.soon |
| Comments |
| Comment by Githook User [ 19/Dec/22 ] |
|
Author: {'name': 'Huayu Ouyang', 'email': 'huayu.ouyang@mongodb.com', 'username': 'huayu-ouyang'}Message: |