|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-11251) Cannot parse coverag... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)
- [JIRA] (JENKINS-11251) Cannot parse co... [email protected] (JIRA)

Notice that in the original reported case, the stack trace includes "determineDocVersion", so this indicates that the pipe was lost very early in the connection. Possibly even before a single byte was read. That sounds like
JENKINS-8703, which was released in remoting 1.420. So if anyone is running older version of master/slave.jar, the first thing to do is to upgrade. But the comment from Philippe indicates that it's still happening in a newer version of Jenkins, so there must be still something going on.JENKINS-7871has different stack trace, and that is happening toward the end of the file.