| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
test-cluster-shared-leak was flaky on Windows 10. Remove unnecessary .send() calls and replace with .disconnect() to avoid spurious EPIPE. Fixes: nodejs#4887 PR-URL: nodejs#4934
|
Here are stress tests with this fix:
Here are stress tests without this fix:
|
Sorry, something went wrong.
Sorry, something went wrong.
|
Confirmed that the test still throws an AssertionError in Node 4.2.1 (which has the bug that this test is written to detect) and runs without throwing any errors in Node 4.2.2 (which has the fix for the bug). $ nvm use 4.2.1
Now using node v4.2.1 (npm v2.14.7)
$ node test/parallel/test-cluster-shared-leak.js
assert.js:89
throw new assert.AssertionError({
^
AssertionError: Resource leak detected.
at removeWorker (cluster.js:328:9)
at ChildProcess.<anonymous> (cluster.js:348:34)
at ChildProcess.g (events.js:260:16)
at emitTwo (events.js:87:13)
at ChildProcess.emit (events.js:172:7)
at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
$ nvm use 4.2.2
Now using node v4.2.2 (npm v2.14.7)
$ node test/parallel/test-cluster-shared-leak.js
$
|
Sorry, something went wrong.
|
CI is green! \o/ |
Sorry, something went wrong.
|
lts watch tag applied. LGTM |
Sorry, something went wrong.
test-cluster-shared-leak was flaky on Windows 10. Remove unnecessary .send() calls and replace with .disconnect() to avoid spurious EPIPE. Fixes: nodejs#4887 PR-URL: nodejs#4934 Reviewed-By: James M Snell <jasnell@gmail.com>
test-cluster-shared-leak was flaky on Windows 10. Remove unnecessary .send() calls and replace with .disconnect() to avoid spurious EPIPE. Fixes: nodejs#4887 PR-URL: nodejs#4934 Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
test: fix flaky cluster test on Windows 10
test-cluster-shared-leak was flaky on Windows 10. Remove unnecessary
.send() calls and replace with .disconnect() to avoid spurious EPIPE.