-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixtures/listen-on-socket-and-exit needs improved cleanup #1543
Labels
test
Issues and PRs related to the tests.
Comments
Just reminding myself that this still seems to be an issue. Found a stray process on one of the smartos machines that's been running from July 2nd (roughly one week). Edit: and one on a freebsd machine. |
thefourtheye
added a commit
to thefourtheye/io.js
that referenced
this issue
Jul 30, 2015
Refer: nodejs#1543 When this test fails, it leaves dead processes in the system. This patch makes sure that the child processes exit first, in case of errors.
thefourtheye
added a commit
that referenced
this issue
Aug 27, 2015
Refer: #1543 When this test fails, it leaves dead processes in the system. This patch makes sure that the child processes exit first, in case of errors. PR-URL: #2206 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Hope #2206 fixed it. Closing for now. |
thefourtheye
added a commit
that referenced
this issue
Aug 28, 2015
Refer: #1543 When this test fails, it leaves dead processes in the system. This patch makes sure that the child processes exit first, in case of errors. PR-URL: #2206 Reviewed-By: Johan Bergström <[email protected]> Reviewed-By: Ben Noordhuis <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While reviewing some of our buildbots, I've found some dead processes which all seems related to failing this test. We need to make cleanup more robust.
The text was updated successfully, but these errors were encountered: