build: make test-ci output TAP to stdout and log

[rvagg]

Roughly the same as #810 but removes message from test-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

[bnoordhuis]

LGTM

[rvagg]

FYI TAP output now in Jenkins: https://jenkins-iojs.nodesource.com/job/iojs+any-pr+multi/190/nodes=iojs-armv7-ubuntu1401/tapTestReport/

[rvagg]

@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 -J a problem here? If I run without -J does parallel actually do anything parallel? It looks to me like perhaps all of the test types are being run in parallel here hence the errors with sockets and pipes.

[indutny]

@rvagg could be related to a stray process that I see locally after make test?

[indutny]

@rvagg this is what I see after make test:

$ ps ax | grep iojs
99139 s003 S 0:00.00 /bin/sh -c "/Users/indutny/Code/indutny/node/out/Release/iojs" "/Users/indutny/Code/indutny/node/test/parallel/test-stdio-closed.js" child 1>&- 2>&-
99140 s003 R 0:00.03 /Users/indutny/Code/indutny/node/out/Release/iojs /Users/indutny/Code/indutny/node/test/parallel/test-stdio-closed.js child
99142 s003 R+ 0:00.00 grep iojs

[indutny]

@bnoordhuis this seems to be your thing b5f25a9

[bnoordhuis]

@indutny It is and I'm seeing that too, FWIW. I'll take a look.