[SERVER-33713] document_source_merge_cursors_test is racy Created: 06/Mar/18 Updated: 29/Oct/23 Resolved: 07/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| 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 | ||||
| Sprint: | Query 2018-03-12 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The test expects that a getMore will be run on two outstanding cursors before any results are returned, but because there is no sort specified, the AsyncResultsMerger can return a result as soon as one of the getMores has returned. The test should be re-written to avoid this race. |
| Comments |
| Comment by Githook User [ 07/Mar/18 ] |
|
Author: {'email': 'charlie.swanson@mongodb.com', 'name': 'Charlie Swanson', 'username': 'cswanson310'}Message: |