mirror of
https://github.com/nodejs/node.git
synced 2024-12-01 16:10:02 +01:00
f29762f4dd
Enable linting for the test directory. A number of changes was made so all tests conform the current rules used by lib and src directories. The only exception for tests is that unreachable (dead) code is allowed. test-fs-non-number-arguments-throw had to be excluded from the changes because of a weird issue on Windows CI. PR-URL: https://github.com/nodejs/io.js/pull/1721 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
31 lines
959 B
JavaScript
31 lines
959 B
JavaScript
'use strict';
|
|
/*
|
|
* This test makes sure that non-integer timer delays do not make the process
|
|
* hang. See https://github.com/joyent/node/issues/8065 and
|
|
* https://github.com/joyent/node/issues/8068 which have been fixed by
|
|
* https://github.com/joyent/node/pull/8073.
|
|
*
|
|
* If the process hangs, this test will make the tests suite timeout,
|
|
* otherwise it will exit very quickly (after 50 timers with a short delay
|
|
* fire).
|
|
*
|
|
* We have to set at least several timers with a non-integer delay to
|
|
* reproduce the issue. Sometimes, a timer with a non-integer delay will
|
|
* expire correctly. 50 timers has always been more than enough to reproduce
|
|
* it 100%.
|
|
*/
|
|
|
|
var assert = require('assert');
|
|
|
|
var TIMEOUT_DELAY = 1.1;
|
|
var NB_TIMEOUTS_FIRED = 50;
|
|
|
|
var nbTimeoutFired = 0;
|
|
var interval = setInterval(function() {
|
|
++nbTimeoutFired;
|
|
if (nbTimeoutFired === NB_TIMEOUTS_FIRED) {
|
|
clearInterval(interval);
|
|
process.exit(0);
|
|
}
|
|
}, TIMEOUT_DELAY);
|