d795301025
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>
35 lines
872 B
JavaScript
35 lines
872 B
JavaScript
'use strict';
|
|
require('../common');
|
|
var assert = require('assert');
|
|
|
|
// setImmediate should run clear its queued cbs once per event loop turn
|
|
// but immediates queued while processing the current queue should happen
|
|
// on the next turn of the event loop.
|
|
|
|
// in v0.10 hit should be 1, because we only process one cb per turn
|
|
// in v0.11 and beyond it should be the exact same size of QUEUE
|
|
// if we're letting things recursively add to the immediate QUEUE hit will be
|
|
// > QUEUE
|
|
|
|
var ticked = false;
|
|
|
|
var hit = 0;
|
|
var QUEUE = 1000;
|
|
|
|
function run() {
|
|
if (hit === 0)
|
|
process.nextTick(function() { ticked = true; });
|
|
|
|
if (ticked) return;
|
|
|
|
hit += 1;
|
|
setImmediate(run);
|
|
}
|
|
|
|
for (var i = 0; i < QUEUE; i++)
|
|
setImmediate(run);
|
|
|
|
process.on('exit', function() {
|
|
console.log('hit', hit);
|
|
assert.strictEqual(hit, QUEUE, 'We ticked between the immediate queue');
|
|
});
|