[SERVER-20798] Wrap sharding calls, which might fail with 'assert.commandWorked' Created: 07/Oct/15 Updated: 10/Dec/15 Resolved: 10/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Sharding B (10/30/15), Sharding C (11/20/15), Sharding D (12/11/15), Sharding E (01/08/16) |
| Participants: |
| Description |
|
This will help us pinpoint the actual place where the failure happened instead of getting some obscure failure later on. |
| Comments |
| Comment by Kaloian Manassiev [ 10/Dec/15 ] |
|
We have been incrementally adding assert.commandWorked to calls in the sharding tests. Closing this ticket, because doing a sweep through all tests at once is impractical and not worth the effort. |
| Comment by Githook User [ 07/Oct/15 ] |
|
Author: {u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}Message: |