[JIRA] (JENKINS-41600) Parallel step running forever if too much console output is logged

[jenk...@philgrayson.com (JIRA)]

Title: Message Title

Phil Grayson commented on JENKINS-41600   Re: Parallel step running forever if too much console output is logged I've also seen this type of issue. A script that outputs large amounts of text at once causes a job to loop forever and continues to grow the job's log file on the Jenkins master. I've not seen it related to Parallel though. Are you able to reproduce this with a single bat command? I've done some debugging and seen this timeout being tripped. Specifically this is causing the timeout (called here). That is copying bytes from the script's output on the slave back to Jenkins master. If it takes longer than 10 seconds for the script's output to be copied, the timeout is triggered and prevents the read byte offset from being updated. Therefore Jenkins master will keep trying to read from the same offset and triggering the timeout. Ideally there would be a way to tell how many bytes have been written in this OutputStream.write call and move the timeout handling so that the `newLocation` variable will accurately say how much script output has really been read. This comment hints that the timeout should be handled in the Remoting library. As a work around, I was able to prevent the bug from affecting my specific test by increasing the timeout to 60 seconds. It's not a suitable general fix though. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.