spurious lint failures in CI

[Trott]

Key line seems to be:

ok 19 - /usr/home/iojs/build/workspace/node-test-lintercat: stdout: Resource temporarily unavailable

See https://ci.nodejs.org/job/node-test-linter/12318/console for an example.

/cc @refack

[gibfahn]

Hmm, maybe the machine can't handle that much console logging.

[gibfahn]

Probably caused by #720 (comment)

[refack]

AFAICT it happened only one (and #720 (comment) is a genius idea!).
RE: "that much console logging" shall I remind you of the 130MB console output for even Windows build ;)

[refack]

I think there's an stdout race of some sort between cat and Jenkins. I just rebuilt that job (https://ci.nodejs.org/job/node-test-linter/12355/console) and got a different truncation:

ok 35 - /usr/home/iojs/buBuild step 'Execute shell' marked build as failure

[refack]

Got an incantation - replace cat with grep -v -P "^(ok|1\.\.|TAP|$)" test-eslint.tap" (no GNU options on smartOS/BSD machines 🤦‍♂️ ), and maybe add an echo --------- for good measure.

[refack]

@Trott to the point of job 12318's failure, see nodejs/node#15805 (comment)

[gibfahn]

Yeah, it's probably due to the speed at which this spewed out 5000 lines of text.

This should be fixed by #720 (comment). I'll close this, reopen if it reoccurs.