[SERVER-56684] initial_sync_fails tests should wait for node to fassert with EXIT_ABRUBT Created: 05/May/21 Updated: 29/Oct/23 Resolved: 01/Jun/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc2, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | post-rc0 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v5.0
|
||||||||
| Sprint: | Repl 2021-05-17, Repl 2021-05-31, Repl 2021-06-14 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 31 | ||||||||
| Description |
|
Right now the initial_sync_fails tests expect the failed node to exit normally, which it usually does as we kill it with SIGTERM. However, if the test runs a bit slow, it may hit an fassert (normal, as initial sync has failed) before the SIGTERM. So we should wait for that fassert to make the test deterministic. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 15/Jun/21 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: (cherry picked from commit 217df06354c42816bde6556000b71b247ffd432f) |
| Comment by Githook User [ 01/Jun/21 ] |
|
Author: {'name': 'Matthew Russotto', 'email': 'matthew.russotto@mongodb.com', 'username': 'mtrussotto'}Message: |