befbbad051
Original commit message: timers: use uv_now instead of Date.now This saves a few calls to gettimeofday which can be expensive, and potentially subject to clock drift. Instead use the loop time which uses hrtime internally. In addition to the backport, this commit: - keeps _idleStart timers' property which is still set to Date.now() to avoid breaking existing code that uses it, even if its use is discouraged. - adds automated tests. These tests use a specific branch of libfaketime that hasn't been submitted upstream yet. libfaketime is git cloned if needed when running automated tests. Signed-off-by: Timothy J Fontaine <tjfontaine@gmail.com>
53 lines
1.6 KiB
JavaScript
53 lines
1.6 KiB
JavaScript
// FaketimeFlags: --exclude-monotonic -f '2014-07-21 09:00:00'
|
|
|
|
var common = require('../common');
|
|
|
|
var Timer = process.binding('timer_wrap').Timer;
|
|
var assert = require('assert');
|
|
|
|
var timerFired = false;
|
|
var intervalFired = false;
|
|
|
|
/*
|
|
* This test case aims at making sure that timing utilities such
|
|
* as setTimeout and setInterval are not vulnerable to time
|
|
* drifting or inconsistent time changes (such as ntp time sync
|
|
* in the past, etc.).
|
|
*
|
|
* It is run using faketime so that we change how
|
|
* non-monotonic clocks perceive time movement. We freeze
|
|
* non-monotonic time, and check if setTimeout and setInterval
|
|
* work properly in that situation.
|
|
*
|
|
* We check this by setting a timer based on a monotonic clock
|
|
* to fire after setTimeout's callback is supposed to be called.
|
|
* This monotonic timer, by definition, is not subject to time drifting
|
|
* and inconsistent time changes, so it can be considered as a solid
|
|
* reference.
|
|
*
|
|
* When the monotonic timer fires, if the setTimeout's callback
|
|
* hasn't been called yet, it means that setTimeout's underlying timer
|
|
* is vulnerable to time drift or inconsistent time changes.
|
|
*/
|
|
|
|
var monoTimer = new Timer();
|
|
monoTimer.ontimeout = function () {
|
|
/*
|
|
* Make sure that setTimeout's and setInterval's callbacks have
|
|
* already fired, otherwise it means that they are vulnerable to
|
|
* time drifting or inconsistent time changes.
|
|
*/
|
|
assert(timerFired);
|
|
assert(intervalFired);
|
|
};
|
|
|
|
monoTimer.start(300, 0);
|
|
|
|
var timer = setTimeout(function () {
|
|
timerFired = true;
|
|
}, 200);
|
|
|
|
var interval = setInterval(function () {
|
|
intervalFired = true;
|
|
clearInterval(interval);
|
|
}, 200);
|