mirror of
https://github.com/nodejs/node.git
synced 2025-05-05 15:32:15 +00:00

Many of the tests use variables to track when callback functions are invoked or events are emitted. These variables are then asserted on process exit. This commit replaces this pattern in straightforward cases with common.mustCall(). This makes the tests easier to reason about, leads to a net reduction in lines of code, and uncovered a few bugs in tests. This commit also replaces some callbacks that should never be called with common.fail(). PR-URL: https://github.com/nodejs/node/pull/7753 Reviewed-By: Wyatt Preul <wpreul@gmail.com> Reviewed-By: Minwoo Jung <jmwsoft@gmail.com> Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
35 lines
998 B
JavaScript
35 lines
998 B
JavaScript
'use strict';
|
|
/*
|
|
* The goal of this test is to cover the Workers' implementation of
|
|
* Worker.prototype.destroy. Worker.prototype.destroy is called within
|
|
* the worker's context: once when the worker is still connected to the
|
|
* master, and another time when it's not connected to it, so that we cover
|
|
* both code paths.
|
|
*/
|
|
|
|
const common = require('../common');
|
|
var cluster = require('cluster');
|
|
var worker1, worker2;
|
|
|
|
if (cluster.isMaster) {
|
|
worker1 = cluster.fork();
|
|
worker2 = cluster.fork();
|
|
|
|
[worker1, worker2].forEach(function(worker) {
|
|
worker.on('disconnect', common.mustCall(function() {}));
|
|
worker.on('exit', common.mustCall(function() {}));
|
|
});
|
|
} else {
|
|
if (cluster.worker.id === 1) {
|
|
// Call destroy when worker is disconnected
|
|
cluster.worker.process.on('disconnect', function() {
|
|
cluster.worker.destroy();
|
|
});
|
|
|
|
cluster.worker.disconnect();
|
|
} else {
|
|
// Call destroy when worker is not disconnected yet
|
|
cluster.worker.destroy();
|
|
}
|
|
}
|