BIND 10 #1024: increase logging verbosity in unittests
BIND 10 Development
do-not-reply at isc.org
Tue Jun 28 17:53:59 UTC 2011
#1024: increase logging verbosity in unittests
-------------------------------------+-------------------------------------
Reporter: | Owner:
jinmei | Status: new
Type: task | Milestone:
Priority: major | Sprint-20110712
Component: | Resolution:
Unclassified | Sensitive: 0
Keywords: | Sub-Project: Core
Defect Severity: N/A | Estimated Difficulty: 0.0
Feature Depending on Ticket: | Total Hours: 0
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Since this feature seemed to be a bit controversial, I'll describe
some more rationale for that.
There can be (and actually was as we saw in #1023) a bug in producing
a debug logging message (or in general log messages at a lower
severity that wouldn't be generated by default). Unless we enable
that level of logging we'll keep missing that type of regression.
There was a suggestion that it would be better to have explicit tests
on logging outputs. I don't deny that, but it doesn't seem to be
possible quickly and would be a kind of middle to long term
enhancements. On the other hand, it's more short term, IMO, to be
able to detect regression in log outputs through our regular tests.
If, in future, separate tests eliminate the need for relying on the
side effect by increasing the log level, we can revert it. But as a
short term improvement I believe we should do it now.
Another note: it would be better to do this ticket after #1071 if
it gets completed quickly. Then we can avoid having a period of
making log output noisier. But if #1071 is not completed, say, within
one week, I suggest we start and complete this task regardless of the
progress of #1071.
--
Ticket URL: <http://bind10.isc.org/ticket/1024#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list