8caa1dcee6
There are several cleanups here that are not just style nits... 1. The `common.isMainThread` was just a passthrough to the `isMainThread` export on the worker_thread module. It's use was inconsistent and just obfuscated the fact that the test file depend on the `worker_threads` built-in. By eliminating it we simplify the test harness a bit and make it clearer which tests depend on the worker_threads check. 2. The `common.isDumbTerminal` is fairly unnecesary since that just wraps a public API check. 3. Several of the `common.skipIf....` checks were inconsistently used and really don't need to be separate utility functions. A key part of the motivation here is to work towards making more of the tests more self-contained and less reliant on the common test harness where possible. PR-URL: https://github.com/nodejs/node/pull/56712 Reviewed-By: Yagiz Nizipli <yagiz@nizipli.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
31 lines
722 B
JavaScript
31 lines
722 B
JavaScript
'use strict';
|
|
|
|
const common = require('../common');
|
|
const assert = require('assert');
|
|
|
|
if (common.isWindows) {
|
|
common.skip('Sending signals with process.kill is not supported on Windows');
|
|
}
|
|
|
|
const { isMainThread } = require('worker_threads');
|
|
|
|
if (!isMainThread) {
|
|
common.skip('No signal handling available in Workers');
|
|
}
|
|
|
|
process.once('SIGINT', common.mustCall((signal) => {
|
|
assert.strictEqual(signal, 'SIGINT');
|
|
}));
|
|
|
|
process.kill(process.pid, 'SIGINT');
|
|
|
|
process.once('SIGTERM', common.mustCall((signal) => {
|
|
assert.strictEqual(signal, 'SIGTERM');
|
|
}));
|
|
|
|
process.kill(process.pid, 'SIGTERM');
|
|
|
|
// Prevent Node.js from exiting due to empty event loop before signal handlers
|
|
// are fired
|
|
setImmediate(() => {});
|