BIND 10 #1482: simple logging format checker using unittests

BIND 10 Development do-not-reply at isc.org
Mon Dec 19 19:15:43 UTC 2011


#1482: simple logging format checker using unittests
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  jinmei                             |                Status:  new
                       Type:  task   |             Milestone:  Next-Sprint-
                   Priority:  major  |  Proposed
                  Component:         |            Resolution:
  logging                            |             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      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:3 vorner]:
 > No, the suggestion looks for the '%' character in the output, looking
 for leftover placeholders I guess. I worry about when the text really does
 contain the character and not as an placeholder.

 Ah, okay, good point.  We could revise it to %[0-9] for example.
 Also, since this is something like a "better than nothing" optional
 check, I think it's okay to run it until we encounter a real false
 positive (at which point we could stop using it until we resolve it).

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


More information about the bind10-tickets mailing list