BIND 10 #1780: time.time() not accurate enough for some recent tests in xfrin

[BIND 10 Development]

#1780: time.time() not accurate enough for some recent tests in xfrin
-------------------------------+-----------------------------------------
            Reporter:  jelte   |                        Owner:  jelte
                Type:  defect  |                       Status:  new
            Priority:  medium  |                    Milestone:  New Tasks
           Component:  xfrin   |                     Keywords:
           Sensitive:  0       |              Defect Severity:  N/A
         Sub-Project:  DNS     |  Feature Depending on Ticket:
Estimated Difficulty:  0       |          Add Hours to Ticket:  0
         Total Hours:  0       |                    Internal?:  0
-------------------------------+-----------------------------------------
 This is not a *big* problem; the relevant tests merely need to check
 whether time has passed. But when calling time.time() twice, fast, the
 difference between them can get rounded down to 0.0 some of the time.

 See for example:
 http://git.bind10.isc.org/~tester/builder//BIND10-cppcheck/20120314083000-FreeBSD8-amd64-GCC/logs/unittests.out

 The code that uses this value takes the possibility of 0 into account,
 btw, but the tests don't. The tests could potentially also fail if time
 went in a negative direction (which is possible if you change your system
 clock).

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