BIND 10 #1482: simple logging format checker using unittests

[BIND 10 Development]

#1482: simple logging format checker using unittests
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  task          |                       Status:  new
            Priority:  major         |                    Milestone:  Next-
           Component:  logging       |  Sprint-Proposed
           Sensitive:  0             |                     Keywords:
         Sub-Project:  Core          |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 To catch some trivial errors in logging like this:
 https://lists.isc.org/pipermail/bind10-dev/2011-December/002897.html
 I'd propose the following:

 - make sure all python unit tests call `isc.log.resetUnitTestRootLogger()`
 - make sure all C++ unit tests call `isc::log::initLogger();
 - add a top level make target, e.g. check-logformat, which would do
 {{{
   B10_LOGGER_DESTINATION=stdout make check
   | grep '^[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9]' |grep '%'
 }}}
    and exits with a non 0 code if the output is not empty
 - fix any current problems that make this target fail
 - configure a buildbot with enabling this target as a regular test

-- 
Ticket URL: <http://bind10.isc.org/ticket/1482>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development