BIND 10 #1024: increase logging verbosity in unittests

[BIND 10 Development]

#1024: increase logging verbosity in unittests
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  vorner
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  major  |  Sprint-20110802
                  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 => vorner


Comment:

 > !LoggerXxxx tests
 There is one message that is unavoidable, as it is generated in a test of
 the logging initialization code (so can't be overridden without affecting
 the initialization under test).

 > log_test.py
 Two messages are generated here that are not easy to suppress.  This code
 tests the Python logging so overriding the logging destination could
 affect the validity of the test.

 > IOFetchTest.!TcpTimeout
 Fixed.

 > bind10_test.py
 > cmdctl_test.py
 > xfrout_test.py
 Done.  Added a resetUnitTestRootLogger() function to be called in the unit
 tests's !__init!__ method that sets the logging parameters to the same as
 those used in the C++ unit tests.

-- 
Ticket URL: <http://bind10.isc.org/ticket/1024#comment:13>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development