BIND 10 #2293: solve frequent BenchMarkTest.run failures

[BIND 10 Development]

#2293: solve frequent BenchMarkTest.run  failures
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  medium        |                    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
-------------------------------------+-------------------------------------
 We have had near 100 timing failures in BenchMarkTest. This is on virtual
 machines: FreeBSD, NetBSD, and Debian5 (but none of the other VMs) and on
 physical Solaris Sparc machine (but no other physical systems).

 Here is an example:

 {{{
 [ RUN      ] BenchMarkTest.run
 benchmark_unittest.cc:119: Failure
 Expected: (sleep_time + duration_margin) > (bench.getDuration() *
 ONE_MILLION), actual: 75000 vs 75077
 benchmark_unittest.cc:125: Failure
 Expected: ((sleep_time + duration_margin) /
 static_cast<double>(sub_iterations)) > (bench.getAverageTime() *
 ONE_MILLION), actual: 3260.8695652173915 vs 3264.217391304348
 benchmark_unittest.cc:128: Failure
 Expected: (static_cast<double>(sub_iterations) / (sleep_time +
 duration_margin)) < (bench.getIterationPerSecond() / ONE_MILLION), actual:
 0.00030666666666666668 vs 0.00030635214513099882
 [  FAILED  ] BenchMarkTest.run (129 ms)
 }}}

 Let's rework this so BenchMarkTest.run does not fail like this anymore.

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