[SERVER-6717] The 'test' program does not log messages in msgasserted() Created: 05/Aug/12 Updated: 11/Jul/16 Resolved: 05/Sep/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Logging |
| Affects Version/s: | None |
| Fix Version/s: | 2.2.1, 2.3.0 |
| Type: | Bug | 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 |
| Operating System: | ALL |
| Participants: |
| Description |
|
The msgasserted() function in util/assert_util.cpp uses tlog() to log messages instead of log(). Because tlogLevel is set to -1 in dbtests/framework.cpp, this suppresses all messages describing the cause of assertions thrown by the 'test' program. It does, however, display stack traces to 'cout', so we get stack traces with no explanation in the output of 'test'. The 'test' logs would be easier to interpret if we could see the reason for the stack traces. Changing 'tlog()' to 'log()' in msgasserted() would fix this. |
| Comments |
| Comment by auto [ 12/Sep/12 ] |
|
Author: {u'date': u'2012-09-03T13:06:07-07:00', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: |
| Comment by auto [ 05/Sep/12 ] |
|
Author: {u'date': u'2012-09-03T13:06:07-07:00', u'email': u'tad@10gen.com', u'name': u'Tad Marshall'}Message: |