-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
build: make test-ci output TAP to stdout and log #938
Conversation
LGTM |
Closes: #810 PR-URL: #938 Reviewed-By: Ben Noordhuis <[email protected]>
FYI TAP output now in Jenkins: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/190/nodes=iojs-armv7-ubuntu1401/tapTestReport/ |
@bnoordhuis @indutny can you have a look at some of the runs after this merge, e.g. https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/193/ Is the |
Closes: nodejs#810 PR-URL: nodejs#938 Reviewed-By: Ben Noordhuis <[email protected]>
@rvagg could be related to a stray process that I see locally after |
@rvagg this is what I see after
|
@bnoordhuis this seems to be your thing b5f25a9 |
@indutny It is and I'm seeing that too, FWIW. I'll take a look. |
Fix parallel/test-stdio-closed introduced in commit b5f25a9 ("src: ensure that file descriptors 0-2 are valid") to not keep spawning child processes ad infinitum. The test spawns itself as a child process but a missing return statement made the child process spawn itself again, and again, and again. It went unnoticed for some time because the child process exits almost immediately afterwards, i.e. it didn't fill up the process table. The observable effect was an iojs process that was quietly consuming CPU cyles in the background with a PID that was constantly changing. Refs: nodejs#938 PR-URL: nodejs#948 Reviewed-By: Fedor Indutny <[email protected]>
Roughly the same as #810 but removes
message
fromtest-ci
so we can actually use it. Produce TAP output and write a test.tap file so Jenkins can pick it up.R= @bnoordhuis
R= @jbergstroem