BIND 10 #267: python log shouldn't die with OSError

[BIND 10 Development]

#267: python log shouldn't die with OSError
--------------------------+-------------------------------------------------
      Reporter:  jinmei   |        Owner:  zzchen_pku                 
          Type:  defect   |       Status:  closed                     
      Priority:  major    |    Milestone:  06. 4th Incremental Release
     Component:  logging  |   Resolution:  fixed                      
      Keywords:           |    Sensitive:  0                          
Estimatedhours:  0.0      |        Hours:                             
      Billable:  1        |   Totalhours:                             
      Internal:  0        |  
--------------------------+-------------------------------------------------
Changes (by zzchen_pku):

  * status:  reviewing => closed
  * resolution:  => fixed


Comment:

 Replying to [comment:18 stephen]:
 > Not really. At the time of writing I had thought about generating a
 unique message in the test - possibly including the date/time the message
 was created so as to distinguish it from other runs of the test - then
 searching the syslog file for that string.  However, the problem here is
 that the name of the syslog file is not standardised, e.g. by default it
 is "syslog" on Ubuntu and "system.log" on OS X. How we check that the
 modules in BIND-10 are logging correctly is a more generalised problem and
 something we should discuss further. I suggest that the code be left as it
 is for now.
 Agree. Thank you for the review.
 Commited. Closing it.

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