[SERVER-85785] Fetch log output after teardown in data_consistency_checks.js Created: 26/Jan/24 Updated: 29/Jan/24 Resolved: 29/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 8.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Xuerui Fa |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Replication
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2024-02-05 | ||||
| Participants: | |||||
| Linked BF Score: | 5 | ||||
| Description |
|
It seems like we first get the output, then shut down the replicaset in data_consistency_checks.js. This can lead to a potential race where the test has not necessarily completed and we have fetched all logs before checking against those logs. |
| Comments |
| Comment by Githook User [ 27/Jan/24 ] |
|
Author: {'name': 'XueruiFa', 'email': 'xuerui.fa@mongodb.com', 'username': 'XueruiFa'}Message: GitOrigin-RevId: 4d404e4156e683825c662b0a56305fc5faa9e227 |