5e5b1f8b89
This brings the node::MakeCallback and node::AsyncWrap::MakeCallback implementations into alignment in that they return early if the nextTickQueue is empty after processing the MicrotaskQueue. Include test to make sure early return happens. Test has text explaining the conditions for the test to pass, since it relies on internal mechanisms that aren't guaranteed in the future. PR-URL: https://github.com/nodejs/node/pull/10274 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
32 lines
1 KiB
JavaScript
32 lines
1 KiB
JavaScript
'use strict';
|
|
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
var allsGood = false;
|
|
var cntr = 0;
|
|
|
|
process.on('exit', () => {
|
|
assert.ok(cntr > 0, '_tickDomainCallback was never called');
|
|
});
|
|
|
|
/**
|
|
* This test relies upon the following internals to work as specified:
|
|
* - require('domain') causes node::Environment::set_tick_callback_function()
|
|
* to use process._tickDomainCallback() to process the nextTickQueue;
|
|
* replacing process._tickCallback().
|
|
* - setImmediate() uses node::MakeCallback() instead of
|
|
* node::AsyncWrap::MakeCallback(). Otherwise the test will always pass.
|
|
* Have not found a way to verify that node::MakeCallback() is used.
|
|
*/
|
|
process._tickDomainCallback = function _tickDomainCallback() {
|
|
assert.ok(allsGood, '_tickDomainCallback should not have been called');
|
|
cntr++;
|
|
};
|
|
|
|
setImmediate(common.mustCall(() => {
|
|
require('domain');
|
|
setImmediate(common.mustCall(() => setImmediate(common.mustCall(() => {
|
|
allsGood = true;
|
|
process.nextTick(() => {});
|
|
}))));
|
|
}));
|