blob: 9a9834aefecc7fa7c20ee859602184562a4c94b6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
|
'use strict';
// FaketimeFlags: --exclude-monotonic -f '2014-07-21 09:00:00'
require('../common');
const Timer = process.binding('timer_wrap').Timer;
const assert = require('assert');
let timerFired = false;
let 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.
*/
const monoTimer = new Timer();
monoTimer[Timer.kOnTimeout] = 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);
setTimeout(function() {
timerFired = true;
}, 200);
const interval = setInterval(function() {
intervalFired = true;
clearInterval(interval);
}, 200);
|
