[SERVER-21214] Dump config server data when the sharded concurrency suites fail Created: 29/Oct/15 Updated: 16/Nov/16 Resolved: 10/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.1, 3.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kamran K. | Assignee: | Judah Schvimer |
| Resolution: | Done | Votes: | 0 |
| Labels: | test-only | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Backport Completed: | |||||
| Sprint: | TIG C (11/20/15), TIG D (12/11/15) | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
Some failures in the sharded concurrency suites can only be debugged if the config server data is available. We should figure out a way to report the data on failure. |
| Comments |
| Comment by Githook User [ 10/Dec/15 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |
| Comment by Githook User [ 10/Dec/15 ] |
|
Author: {u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}Message: |