[SERVER-32053] explain3.js should assert that its writes succeed Created: 21/Nov/17 Updated: 30/Oct/23 Resolved: 04/Dec/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.1, 3.7.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (Inactive) | Assignee: | James Wahlin |
| 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 | ||||||||
| Backport Requested: |
v3.6
|
||||||||
| Sprint: | Query 2017-12-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The explain3.js test does not check that its writes succeed, but expects all documents to be inserted at the end of the test. If a stepdown occurs, causing writes to fail, then fewer documents will be present at the end of the test. The test also does not assert anything about the behavior of an explain that is concurrent with a dropIndex. If we feel this is important to test, we should improve the test to make assertions, rather than just printing any exceptions the explain throws. |
| Comments |
| Comment by Githook User [ 08/Dec/17 ] |
|
Author: {'name': 'James Wahlin', 'email': 'james@mongodb.com', 'username': 'jameswahlin'}Message: (cherry picked from commit 7920e242c0def907b502265ca14ddf3d86c98025) |
| Comment by Githook User [ 04/Dec/17 ] |
|
Author: {'username': 'jameswahlin', 'email': 'james@mongodb.com', 'name': 'James Wahlin'}Message: |