-
-
Notifications
You must be signed in to change notification settings - Fork 35.3k
Investigate cluster/child_process oddity on macOS #14828
Copy link
Copy link
Closed
Labels
child_processIssues and PRs related to the child_process subsystem.Issues and PRs related to the child_process subsystem.clusterIssues and PRs related to the cluster subsystem.Issues and PRs related to the cluster subsystem.flaky-testIssues and PRs related to the tests with unstable failures on the CI.Issues and PRs related to the tests with unstable failures on the CI.macosIssues and PRs related to the macOS platform / OSX.Issues and PRs related to the macOS platform / OSX.
Metadata
Metadata
Assignees
Labels
child_processIssues and PRs related to the child_process subsystem.Issues and PRs related to the child_process subsystem.clusterIssues and PRs related to the cluster subsystem.Issues and PRs related to the cluster subsystem.flaky-testIssues and PRs related to the tests with unstable failures on the CI.Issues and PRs related to the tests with unstable failures on the CI.macosIssues and PRs related to the macOS platform / OSX.Issues and PRs related to the macOS platform / OSX.
Version: 9.0.0-pre
Platform: macOS 10.x (seen on 10.10, 10.11, and 10.12)
Subsystem: cluster child_process
A workaround/fix was introduced to test-cluster-send-handle-large-payload in #14780 so that it wouldn't time out on macOS from time to time.
It's not clear if this behavior is a bug in the test, a bug in Node.js, a bug in macOS, or simply not a bug at all.
dtruss -f output
Success: https://gist.github.com/Trott/e32e1a48c84a9fdba09177e90bda05d4
Failure: https://gist.github.com/Trott/fb77e052ff369e33d1b18f5ad9492ba9 (terminated with cntl-c after it hung for a while, if that matters)
Additional info from #14747
Code from version of test without the fix/workaround:
/cc @addaleax