You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ;)
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.
Activity
gibfahn commentedon Oct 8, 2017
Hmm, maybe the machine can't handle that much console logging.
gibfahn commentedon Oct 8, 2017
Probably caused by #720 (comment)
refack commentedon Oct 8, 2017
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 commentedon Oct 8, 2017
I think there's an stdout race of some sort between
catand Jenkins. I just rebuilt that job (https://ci.nodejs.org/job/node-test-linter/12355/console) and got a different truncation:refack commentedon Oct 8, 2017
Got an incantation - replace
catwith(no GNU options on smartOS/BSD machines 🤦♂️ ), and maybe add angrep -v -P "^(ok|1\.\.|TAP|$)" test-eslint.tap"echo ---------for good measure.refack commentedon Oct 8, 2017
@Trott to the point of job 12318's failure, see nodejs/node#15805 (comment)
gibfahn commentedon Oct 8, 2017
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.