BIND 10 #1024: increase logging verbosity in unittests
BIND 10 Development
do-not-reply at isc.org
Thu Jul 7 16:57:23 UTC 2011
#1024: increase logging verbosity in unittests
-------------------------------------+-------------------------------------
Reporter: | Owner: jreed
jinmei | Status: reviewing
Type: task | Milestone:
Priority: major | Sprint-20110712
Component: | Resolution:
logging | Sensitive: 0
Keywords: | Sub-Project: Core
Defect Severity: N/A | Estimated Difficulty: 0.5
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Changes (by stephen):
* owner: stephen => jreed
Comment:
> Way too much noise by default. Well over 24,000 log lines (even with
incomplete run). Please by default just log to /dev/null.
Done. To make the output visible, set the environment variable
B10_LOGGER_DESTINATION to stdout or stderr. (I'll send an email round to
bind10-dev to flag this and update the page in the wiki before I merge.)
> I am not sure if this was introduced in this trac1024 branch, but I
don't recall seeing it previously ...
This problem was fixed in #1084. Prior to making this change (to log to
/dev/null by default), I merged master into the branch. When you run the
test, this should be fixed.
--
Ticket URL: <http://bind10.isc.org/ticket/1024#comment:10>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list