Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33610

IOException with Clover 4.6 plugin

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: clover-plugin
    • Labels:
      None
    • Environment:
      clover plugin 4.6
      jenkins 1.648
    • Similar Issues:

      Description

      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...

      The coverage reports seem to be published back to the master correctly despite the IOException.

        Attachments

          Activity

          trbaker Trevor Baker created issue -
          trbaker Trevor Baker made changes -
          Field Original Value New Value
          Description 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...
          ```
          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}
          trbaker Trevor Baker made changes -
          Description 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}
          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...
          }}
          trbaker Trevor Baker made changes -
          Description 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...
          }}
          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}
          trbaker Trevor Baker made changes -
          Description 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}
          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.
          rmiesen Robert Miesen made changes -
          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. ]
          stephenconnolly Stephen Connolly made changes -
          Assignee stephenconnolly [ stephenconnolly ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 169569 ] JNJira + In-Review [ 183548 ]
          Hide
          lukaswoj Łukasz Wojciechowski added a comment -

          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

          Show
          lukaswoj Łukasz Wojciechowski added a comment - 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
          Hide
          mparfianowicz Marek Parfianowicz added a comment -

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

          Łukasz Wojciechowski: 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.

          Show
          mparfianowicz Marek Parfianowicz added a comment - Trevor Baker : would you able to get the full stack trace for this error? Łukasz Wojciechowski : 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.
          Hide
          lukaswoj Łukasz Wojciechowski added a comment -

          Marek Parfianowicz - sorry but it looks like I lied in my previous comment.
          After I removed "Archiving Artifacts" - I still see the same exception being thrown.
          The difference, though is that it does no longer causes build to end up with FAILURE state - this is why I missed that fact.
          When my build turned from red to green I blindly assumed the exception is gone but apparently this is not the case.

          I would happily provide a stack trace but I need guidance on how to produce it. Not sure why in this case stack trace is missing. Within our Jenkins setup, other exceptions that occurs sometimes have full stack trace shown "by default".

          Show
          lukaswoj Łukasz Wojciechowski added a comment - Marek Parfianowicz - sorry but it looks like I lied in my previous comment. After I removed "Archiving Artifacts" - I still see the same exception being thrown. The difference, though is that it does no longer causes build to end up with FAILURE state - this is why I missed that fact. When my build turned from red to green I blindly assumed the exception is gone but apparently this is not the case. I would happily provide a stack trace but I need guidance on how to produce it. Not sure why in this case stack trace is missing. Within our Jenkins setup, other exceptions that occurs sometimes have full stack trace shown "by default".
          Hide
          nancychopra Nancy Chopra added a comment -

          I am facing the same issue. Could this be causing the clover xml to not be parsed? The build status is marked as green no matter what the thresh hold is.

          Show
          nancychopra Nancy Chopra added a comment - I am facing the same issue. Could this be causing the clover xml to not be parsed? The build status is marked as green no matter what the thresh hold is.
          Hide
          markcariddi Mark Cariddi added a comment -

          I see the XML published by I am not able to see the bullseye coverate report.   

          Show
          markcariddi Mark Cariddi added a comment - I see the XML published by I am not able to see the bullseye coverate report.   
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Marek Parfianowicz
          Path:
          src/main/java/hudson/plugins/clover/CloverPublisher.java
          src/main/java/hudson/plugins/clover/slave/GetPathFileCallable.java
          http://jenkins-ci.org/commit/clover-plugin/c356a20e9f14da32db36194a2e80e1827ead0c44
          Log:
          JENKINS-33610: extracted anonymous class to lop-level to get rid of
          NoClassDefFoundError: hudson/plugins/clover/CloverPublisher$1'; added more logging

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Marek Parfianowicz Path: src/main/java/hudson/plugins/clover/CloverPublisher.java src/main/java/hudson/plugins/clover/slave/GetPathFileCallable.java http://jenkins-ci.org/commit/clover-plugin/c356a20e9f14da32db36194a2e80e1827ead0c44 Log: JENKINS-33610 : extracted anonymous class to lop-level to get rid of NoClassDefFoundError: hudson/plugins/clover/CloverPublisher$1'; added more logging
          marekparf Marek Parfianowicz made changes -
          Status Open [ 1 ] In Progress [ 3 ]
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Marek Parfianowicz
          Path:
          src/main/java/hudson/plugins/clover/CloverPublisher.java
          http://jenkins-ci.org/commit/clover-plugin/df5b18dc7a8a667464f522c8f9bc3963d645140f
          Log:
          JENKINS-33610: println

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Marek Parfianowicz Path: src/main/java/hudson/plugins/clover/CloverPublisher.java http://jenkins-ci.org/commit/clover-plugin/df5b18dc7a8a667464f522c8f9bc3963d645140f Log: JENKINS-33610 : println
          Hide
          marekparf Marek Parfianowicz added a comment -

          I had a different exception in the log, but after my change I don't see any errors with remote agents.

          I think the change should fix the problem reported by you. I think that because the hudson/plugins/clover/CloverPublisher$1 was an anonymous inner class, so it had a reference to an enclosing class, i.e. the CloverPublisher which does not implement Serializable interface.

          And the most probably the CloverPublisher$1 (now renamed to GetPathFileCallable, which implements SlaveToMasterFileCallable) was called by the FileCallableWrapper mentioned in the bug description.

          Show
          marekparf Marek Parfianowicz added a comment - I had a different exception in the log, but after my change I don't see any errors with remote agents. I think the change should fix the problem reported by you. I think that because the hudson/plugins/clover/CloverPublisher$1 was an anonymous inner class, so it had a reference to an enclosing class, i.e. the CloverPublisher which does not implement Serializable interface. And the most probably the CloverPublisher$1 (now renamed to GetPathFileCallable, which implements SlaveToMasterFileCallable) was called by the FileCallableWrapper mentioned in the bug description.
          Hide
          marekparf Marek Parfianowicz added a comment -

          Fix will be delivered in 4.8.1+

          Show
          marekparf Marek Parfianowicz added a comment - Fix will be delivered in 4.8.1+
          marekparf Marek Parfianowicz made changes -
          Status In Progress [ 3 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]

            People

            • Assignee:
              Unassigned
              Reporter:
              trbaker Trevor Baker
            • Votes:
              12 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: