[SERVER-48339] Ensure operation is hung on failpoint in unionWith_current_op.js Created: 20/May/20 Updated: 29/Oct/23 Resolved: 10/Jul/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.1, 4.7.0 |
| Type: | Improvement | 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 | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Participants: | |||||||||
| Linked BF Score: | 7 | ||||||||
| Description |
|
The test is trying to verify that $unionWith will show up in the $currentOp output as expected. To do so, it waits for the operation to hang on a failpoint. Unfortunately, the way it checks to see if the operation is hung does not ensure it's actually hit the failpoint yet, it just checks to see it present in the $currentOp output. If the operation fails and needs to be retried for some reason, it will not hit the failpoint. The failpoint it uses hangs only after a command completes successfully. Adding a filter on the "failpointMsg" in the $currentOp output should ensure the test is in the state it expects before proceeding. |
| Comments |
| Comment by Githook User [ 05/Aug/20 ] |
|
Author: {'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}Message: (cherry picked from commit ff8a74db8a39fbc89bb25fee964dc2d1173acacd) |
| Comment by Githook User [ 10/Jul/20 ] |
|
Author: {'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com', 'username': 'cswanson310'}Message: |