node/test/report/test-report-signal.js
cjihrig 9d1a3b6f60
doc,lib,src,test: make --experimental-report a nop
This commit makes the --experimental-report CLI flag a no-op.

PR-URL: https://github.com/nodejs/node/pull/32242
Fixes: https://github.com/nodejs/node/issues/26293
Reviewed-By: Richard Lau <riclau@uk.ibm.com>
Reviewed-By: David Carlier <devnexen@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
2020-03-15 13:29:34 -04:00

34 lines
1010 B
JavaScript

// Flags: --report-on-signal
'use strict';
// Test producing a report via signal.
const common = require('../common');
if (common.isWindows)
return common.skip('Unsupported on Windows.');
if (!common.isMainThread)
common.skip('Signal reporting is only supported in the main thread');
const assert = require('assert');
const helper = require('../common/report');
const tmpdir = require('../common/tmpdir');
tmpdir.refresh();
process.report.directory = tmpdir.path;
assert.strictEqual(process.listenerCount('SIGUSR2'), 1);
process.kill(process.pid, 'SIGUSR2');
// Asynchronously wait for the report. In development, a single setImmediate()
// appears to be enough. Use an async loop to be a bit more robust in case
// platform or machine differences throw off the timing.
(function validate() {
const reports = helper.findReports(process.pid, tmpdir.path);
if (reports.length === 0)
return setImmediate(validate);
assert.strictEqual(reports.length, 1);
helper.validate(reports[0]);
})();