BIND 10 #1016: IntervalTimerTest shouldn't rely on the accuracy of the timer

[BIND 10 Development]

#1016: IntervalTimerTest shouldn't rely on the accuracy of the timer
-------------------------------------+-------------------------------------
            Reporter:  y-aharen      |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  minor         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           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
-------------------------------------+-------------------------------------
 There're two tests which rely on the accuracy of the timer:
 * !IntervalTimerTest.startIntervalTimer
 * !IntervalTimerTest.overwriteIntervalTimer

 The intention of the tests is not to test asio::deadline_timer, to test
 asiolink::!IntervalTimer. Occasional failure of the tests can be solved
 with the following modifications.

 * !IntervalTimerTest.startIntervalTimer
   * Test if the call back function will be called after the specified
 interval or longer instead of checking the elapsed time is within +/- 50
 msec.

 * !IntervalTimerTest.overwriteIntervalTimer
   * Test if the return value of getInterval() will be updated after
 calling setup() instead of measuring the time

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