[SERVER-8444] Print stack trace when ReplSetTest.getMaster() fails Created: 03/Feb/13 Updated: 11/Jul/16 Resolved: 07/Feb/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.0-rc1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Tad Marshall | Assignee: | Tad Marshall |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
It is hard to debug some test failures because there isn't enough information logged to see where a failure happened. The ReplSetTest JavaScript module calls its own getMaster() routine from many places, and users of ReplSetTest also call it. Because it is not based on any of the assert() functions, it prints no stack trace when it throws an exception, so there is no way to tell what function was calling it when it failed. getMaster() should print a stack trace on failure to help debugging. |
| Comments |
| Comment by auto [ 07/Feb/13 ] |
|
Author: {u'date': u'2013-02-03T01:32:06Z', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: |