• Type: Bug
• Resolution: Fixed
• Priority: Minor
• Component/s: clover-plugin
• Labels:

  None
• Environment:

  clover plugin 4.6
  jenkins 1.648
  

[JENKINS-33610] IOException with Clover 4.6 plugin

Trevor Baker created issue - 2016-03-17 09:05

Trevor Baker made changes - 2016-03-17 09:05

Description

Original: I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave ``` Archiving artifacts Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... IOException when checking workspace path:remote file operation failed: <the path> at hudson.remoting.Channel@69b58179:<the slavee>: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9 Publishing Clover coverage results... ```

New: I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave {quote} Archiving artifacts Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... IOException when checking workspace path:remote file operation failed: <the path> at hudson.remoting.Channel@69b58179:<the slavee>: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9 Publishing Clover coverage results... {quote}

Trevor Baker made changes - 2016-03-17 09:06

Description

Original: I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave {quote} Archiving artifacts Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... IOException when checking workspace path:remote file operation failed: <the path> at hudson.remoting.Channel@69b58179:<the slavee>: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9 Publishing Clover coverage results... {quote}

New: I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave {{Archiving artifacts Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... IOException when checking workspace path:remote file operation failed: /home/ec2-user/jenkins/workspace/the-job at hudson.remoting.Channel@69b58179:<the slave>: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9 Publishing Clover coverage results... }}

Trevor Baker made changes - 2016-03-17 09:07

Description

Original: I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave {{Archiving artifacts Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... IOException when checking workspace path:remote file operation failed: /home/ec2-user/jenkins/workspace/the-job at hudson.remoting.Channel@69b58179:<the slave>: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9 Publishing Clover coverage results... }}

New: I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave {quote} Archiving artifacts Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... IOException when checking workspace path:remote file operation failed: /home/ec2-user/jenkins/workspace/the-job at hudson.remoting.Channel@69b58179:<the slave>: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9 Publishing Clover coverage results... {quote}

Trevor Baker made changes - 2016-03-17 09:08

Description

Original: I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave {quote} Archiving artifacts Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... IOException when checking workspace path:remote file operation failed: /home/ec2-user/jenkins/workspace/the-job at hudson.remoting.Channel@69b58179:<the slave>: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9 Publishing Clover coverage results... {quote}

New: I am seeing a new IOException since upgrading to v4.60 of the clover plugin in a job running on a linux ec2 slave {quote} Archiving artifacts Publishing Clover coverage report... Publishing Clover HTML report... Publishing Clover XML report... IOException when checking workspace path:remote file operation failed: /home/ec2-user/jenkins/workspace/the-job at hudson.remoting.Channel@69b58179:<the slave>: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@4836f4e9 Publishing Clover coverage results... {quote} The coverage reports seem to be published back to the master correctly despite the IOException.

Robert Miesen made changes - 2016-03-25 22:07

Comment

[ I can confirm that we are experiencing the same issues after we upgraded the clover plugin to version 4.6. We are running Jenkins 1.642.2 LTS. ]

Stephen Connolly made changes - 2016-07-13 08:19

Assignee

Original: Stephen Connolly [ stephenconnolly ]

R. Tyler Croy made changes - 2016-07-25 23:52

Workflow

Original: JNJira [ 169569 ]

New: JNJira + In-Review [ 183548 ]

Collapse comment: Łukasz Wojciechowski added a comment - 2017-01-23 10:28

Łukasz Wojciechowski added a comment - 2017-01-23 10:28

Hi there,

I was dealing with the same problem.
I'm using latest, 4.7.1 version.
Not sure how this is related but the error is gone after I removed "Archiving artifacts" step.
And it did not matter if I had it before or after "Clover Publisher" step.

I hope this will be helpful to anyone

Expand comment: Łukasz Wojciechowski added a comment - 2017-01-23 10:28

Łukasz Wojciechowski added a comment - 2017-01-23 10:28 Hi there, I was dealing with the same problem. I'm using latest, 4.7.1 version. Not sure how this is related but the error is gone after I removed "Archiving artifacts" step. And it did not matter if I had it before or after "Clover Publisher" step. I hope this will be helpful to anyone

Collapse comment: Marek Parfianowicz added a comment - 2017-01-23 11:09

Marek Parfianowicz added a comment - 2017-01-23 11:09

trbaker: would you able to get the full stack trace for this error?

lukaswoj: thanks for the hint; I suspect that it's either some network error or that Clover unintentionally uses some non-serialisable class

I can investigate it but not sooner than in February. Feel free to grab code from github.com/jenkinsci/clover-plugin to debug it if you wish.

Expand comment: Marek Parfianowicz added a comment - 2017-01-23 11:09

Marek Parfianowicz added a comment - 2017-01-23 11:09 trbaker : would you able to get the full stack trace for this error? lukaswoj : thanks for the hint; I suspect that it's either some network error or that Clover unintentionally uses some non-serialisable class I can investigate it but not sooner than in February. Feel free to grab code from github.com/jenkinsci/clover-plugin to debug it if you wish.

Load more newer events