GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — test: fix flaky test-child-process-exec-timeout · nodejs/node@7af8738

File tree

Expand file treeCollapse file tree
Open diff view settings
Filter options
  • test/parallel
    • test-child-process-exec-timeout.js
Expand file treeCollapse file tree
Open diff view settings
Collapse file

‎test/parallel/test-child-process-exec-timeout.js‎

Copy file name to clipboardExpand all lines: test/parallel/test-child-process-exec-timeout.js
+7-1Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,13 @@ const cmd = `${process.execPath} ${__filename} child`;
1818
cp.exec(cmd, { timeout: 1 }, common.mustCall((err, stdout, stderr) => {
1919
assert.strictEqual(err.killed, true);
2020
assert.strictEqual(err.code, null);
21-
assert.strictEqual(err.signal, 'SIGTERM');
21+
// At least starting with Darwin Kernel Version 16.4.0, sending a SIGTERM to a
22+
// process that is still starting up kills it with SIGKILL instead of SIGTERM.
23+
// See: https://github.com/libuv/libuv/issues/1226
24+
if (common.isOSX)
25+
assert.ok(err.signal === 'SIGTERM' || err.signal === 'SIGKILL');
26+
else
27+
assert.strictEqual(err.signal, 'SIGTERM');
2228
assert.strictEqual(err.cmd, cmd);
2329
assert.strictEqual(stdout.trim(), '');
2430
assert.strictEqual(stderr.trim(), '');

0 commit comments

Comments
0 (0)
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.