[SERVER-62979] Make fall_off_capped_collection_yielding.js test more robust Created: 25/Jan/22 Updated: 29/Oct/23 Resolved: 17/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Sprint: | QE 2022-02-07, QE 2022-02-21 | ||||
| Participants: | |||||
| Linked BF Score: | 7 | ||||
| Description |
|
Since the classic engine checks for interrupt/yield after NEED_TIME is returned by the PlanStages, it is possible that the query yields in this test before any data is accessed. If this happens, no CappedCollectionLost error will be raised, which will cause the test to fail. |
| Comments |
| Comment by Githook User [ 27/Jan/22 ] |
|
Author: {'name': 'Ian Boros', 'email': 'ian.boros@mongodb.com', 'username': 'borosaurus'}Message: |