| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
last test: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/814/ re-test after rebase: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/815/ |
Sorry, something went wrong.
|
LGTM. Verified on a machine I could reproduce on prior to patch. |
Sorry, something went wrong.
|
Timeout error of test-cluster-worker-wait-server-close.js on my FreeBSD machine was resolved with this patch. |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
Wait for data to arrive from worker before doing a disconnect. Without this, whether the disconnect arrives at the worker before the master accepts and forwards the connection descriptor to the worker is a race.
|
Landed in a5987d4d5e21be04a6239579634fa8b19446d5ef |
Sorry, something went wrong.
|
@sam-github I can't find this commit in the master branch. Github doesn't either. Confuserating. |
Sorry, something went wrong.
$ git fetch -q iojs && git branch -a --contains a5987d4d5e21be04a6239579634fa8b19446d5ef
error: no such commit a5987d4d5e21be04a6239579634fa8b19446d5ef |
Sorry, something went wrong.
|
I think I figured out what's going on. You pushed it to your own master branch, but for some reason the generated github link thinks the commit also lives in the nodejs/io.js repo (which it doesn't). |
Sorry, something went wrong.
|
@sam-github |
Sorry, something went wrong.
Wait for data to arrive from worker before doing a disconnect. Without this, whether the disconnect arrives at the worker before the master accepts and forwards the connection descriptor to the worker is a race. Reviewed-By: Sam Roberts <vieuxtech@gmail.com> Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Rod Vagg <rod@vagg.org> PR-URL: #1953 Fixes: #1933 Fixes: #1400
|
Landed in 03ce84d Sorry for the confusion |
Sorry, something went wrong.
|
Probably not related to this specific test, but part of the same problem: Two freebsd bots saw this issue in a recent run: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/842/ I couldn't find any trailing processes on either machine. Could it possibly be some other test opening it and now being closed by this fix? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
fix #1933
replaces #1934
passed all tests except arm7 and raspberry pi 1 and 2, they are still ongoing
@Olegas @trevnorris PTAL
note that I think there are ALSO bugs in cluster message passing... this test attempts to evade them by waiting for the socket to be definitively open... by waiting for data from the worker/server