benchmark: check for time precision in common.js

Some benchmark tests are failing intermittently, possibly due to hrtime() imprecision on particular hosts. This change will confirm or refute that as the root cause the next time the test fails on CI. Either way, it's a valid check. PR-URL: #12934 Ref: #12497 Ref: #12433 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Joyee Cheung <[email protected]> Reviewed-By: James M Snell <[email protected]>
nodejs · May 11, 2017 · a82e0e6 · a82e0e6
1 parent 6f449db
commit a82e0e6
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/benchmark/common.js b/benchmark/common.js
@@ -196,6 +196,9 @@ Benchmark.prototype.end = function(operations) {
   if (!process.env.NODEJS_BENCHMARK_ZERO_ALLOWED && operations <= 0) {
     throw new Error('called end() with operation count <= 0');
   }
+  if (elapsed[0] === 0 && elapsed[1] === 0) {
+    throw new Error('insufficient time precision for short benchmark');
+  }
 
   const time = elapsed[0] + elapsed[1] / 1e9;
   const rate = operations / time;