BIND 10 #1170: TTL checks in resolver tests may be too restrictive

[BIND 10 Development]

#1170: TTL checks in resolver tests may be too restrictive
---------------------------------+-----------------------------------------
            Reporter:  shane     |                        Owner:
                Type:  defect    |                       Status:  new
            Priority:  minor     |                    Milestone:  New Tasks
           Component:  resolver  |                     Keywords:
           Sensitive:  0         |              Defect Severity:  Low
         Sub-Project:  DNS       |  Feature Depending on Ticket:
Estimated Difficulty:  0         |          Add Hours to Ticket:  0
         Total Hours:  0         |                    Internal?:  0
---------------------------------+-----------------------------------------
 Jeremy pointed out a recent test failure:

 http://git.bind10.isc.org/~tester/builder//BIND10-systest/20110811124500-MacOS/logs/unittests.out

 Looked at the tests, and it seems like all of the values for TTL are based
 on whole second values. This means that if a test happens to run near the
 end of a given second, that the second may change during that second, and
 the TTL should go down by 1, as we see there.

 Note that this theory may be based on my poor understanding of how TTLs
 are tracked!

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