common.js needs to be loaded in all tests so that there is checking for variable leaks and possibly other things. However, it does not need to be assigned to a variable if nothing in common.js is referred to elsewhere in the test. The main tradeoff for this bit of code churn is that it gets the code base most of the way to being able to enable the no-unused-vars rule in eslint. (The non-tooling benefit is that it lessens cognitive load when reading tests as it is an immediate indication that none of the functions or properties in common.js will be used by the test.) PR-URL: https://github.com/nodejs/node/pull/4563 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
44 lines
922 B
JavaScript
44 lines
922 B
JavaScript
'use strict';
|
|
require('../common');
|
|
var assert = require('assert');
|
|
|
|
// this is the inverse of test-next-tick-starvation.
|
|
// it verifies that process.nextTick will *always* come before other
|
|
// events, up to the limit of the process.maxTickDepth value.
|
|
|
|
// WARNING: unsafe!
|
|
process.maxTickDepth = Infinity;
|
|
|
|
var ran = false;
|
|
var starved = false;
|
|
var start = +new Date();
|
|
var timerRan = false;
|
|
|
|
function spin() {
|
|
ran = true;
|
|
var now = +new Date();
|
|
if (now - start > 100) {
|
|
console.log('The timer is starving, just as we planned.');
|
|
starved = true;
|
|
|
|
// now let it out.
|
|
return;
|
|
}
|
|
|
|
process.nextTick(spin);
|
|
}
|
|
|
|
function onTimeout() {
|
|
if (!starved) throw new Error('The timer escaped!');
|
|
console.log('The timer ran once the ban was lifted');
|
|
timerRan = true;
|
|
}
|
|
|
|
spin();
|
|
setTimeout(onTimeout, 50);
|
|
|
|
process.on('exit', function() {
|
|
assert.ok(ran);
|
|
assert.ok(starved);
|
|
assert.ok(timerRan);
|
|
});
|