-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins core 2.85
testInProgress 1.4
Starting with Jenkins core 2.85, testInProgress does not show anything when clicking on the "Test progress report" action. The Log file says:
Dez 08, 2017 7:47:40 AM org.jenkinsci.testinprogress.server.messages.AllVersionsTestMessagesParser processTestMessages WARNUNG: Could not read message java.io.IOException: Unknown message format : at org.jenkinsci.testinprogress.server.messages.AllVersionsTestMessagesParser.processTestMessages(AllVersionsTestMessagesParser.java:45) at org.jenkinsci.testinprogress.server.events.TestEventsReceiver.run(TestEventsReceiver.java:41) at java.lang.Thread.run(Thread.java:748)
Also, there are no longer .events files under unitevents/. As far as I can tell, it seems like it has to do with changes on the remoting version, introduced with the Jenkins core 2.85.
[JENKINS-48446] TestInProgress stopped working with Jenkins core 2.85
With core version 2.98:
Jenkins system log:
Jan 04, 2018 8:57:37 AM WARNING org.jenkinsci.testinprogress.server.messages.AllVersionsTestMessagesParser processTestMessages Could not read message java.io.IOException: Unknown message format : at org.jenkinsci.testinprogress.server.messages.AllVersionsTestMessagesParser.processTestMessages(AllVersionsTestMessagesParser.java:45) at org.jenkinsci.testinprogress.server.events.TestEventsReceiver.run(TestEventsReceiver.java:41) at java.lang.Thread.run(Thread.java:745)
Agent log:
Jan 04, 2018 8:57:37 AM hudson.remoting.forward.CopyThread run WARNING: Exception while copying in thread: Copier for /127.0.0.1:36072 java.io.IOException: stream is already closed at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:103) at hudson.remoting.RemoteOutputStream.write(RemoteOutputStream.java:108) at hudson.remoting.forward.CopyThread.run(CopyThread.java:46)
Remoting version: 3.15
I also tried it with core 2.85, remoting version 3.13 and no additional agents connected (building on master). Same behavior.
Jeff Thompson
added a comment - There isn't sufficient information to progress with this as a remoting issue. It doesn't look there is much interest in the testinprogress-plugin either so it's unlikely that we'll get more information from that side. I'll remove Remoting from this ticket. I someone wants to bring testinprogress-plugin up to date and still encounters issues relating to Remoting, we can address those.
Jeff Thompson
added a comment - There isn't sufficient information to progress with this as a remoting issue. It doesn't look there is much interest in the testinprogress-plugin either so it's unlikely that we'll get more information from that side. I'll remove Remoting from this ticket. I someone wants to bring testinprogress-plugin up to date and still encounters issues relating to Remoting, we can address those. 
Due to whatever reason firstMessage is an empty string in https://github.com/jenkinsci/testInProgress-plugin/blob/master/server/src/main/java/org/jenkinsci/testinprogress/server/messages/AllVersionsTestMessagesParser.java#L26 . Likely it means that the reader gets closed.
jochenafuerbacher if you suspect a Remoting regression, please attach:
1) Jenkins system logs
2) Agent logs from the agent filesystem (see https://github.com/jenkinsci/remoting/blob/master/docs/logging.md)
3) Remoting version
Maybe there is just an agent disconnect