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

Regression issue in Warnings Plugin

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • warnings-plugin
    • None
    • Jenkins is running on Win32 / XP
      The jobs are running on the master or a client node.
      Jenkins has been updated to the latest version (v.1.418) and all plugins are up-to-date

      When updating the Warnings plugin from 3.16 to 3.17 or above, I've noticed that the plugin was giving the following error:
      Note that:

      • Our project has a lot of warnings (2338 warnings)
      • It 'seems' to happen independently of the job running on the master or a client node.

      -------------------

      ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception
      hudson.util.IOException2: remote file operation failed: c:\hudson\workspace\ViCE2_C_Model at hudson.remoting.Channel@1f2afad:lbmht-flis2
      at hudson.FilePath.act(FilePath.java:754)
      at hudson.FilePath.act(FilePath.java:740)
      at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:235)
      at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:310)
      at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
      at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:664)
      at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:639)
      at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:617)
      at hudson.model.Build$RunnerImpl.post2(Build.java:161)
      at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:586)
      at hudson.model.Run.run(Run.java:1400)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:175)
      Caused by: java.io.IOException: Remote call on lbmht-flis2 failed
      at hudson.remoting.Channel.call(Channel.java:672)
      at hudson.FilePath.act(FilePath.java:747)
      ... 13 more
      Caused by: java.lang.ClassNotFoundException: Failed to deserialize the Callable object. Perhaps you needed to implement DelegatingCallable?
      at hudson.remoting.UserRequest.perform(UserRequest.java:100)
      at hudson.remoting.UserRequest.perform(UserRequest.java:48)
      at hudson.remoting.Request$2.run(Request.java:270)
      at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
      at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
      at java.util.concurrent.FutureTask.run(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at hudson.remoting.Engine$1$1.run(Engine.java:60)
      at java.lang.Thread.run(Unknown Source)
      Caused by: java.lang.ClassNotFoundException: hudson.plugins.warnings.parser.FileWarningsParser
      at java.net.URLClassLoader$1.run(Unknown Source)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.net.URLClassLoader.findClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
      at java.lang.ClassLoader.loadClass(Unknown Source)
      at java.lang.Class.forName0(Native Method)
      at java.lang.Class.forName(Unknown Source)
      at java.io.ObjectInputStream.resolveClass(Unknown Source)
      at hudson.remoting.ObjectInputStreamEx.resolveClass(ObjectInputStreamEx.java:50)
      at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
      at java.io.ObjectInputStream.readClassDesc(Unknown Source)
      at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
      at java.io.ObjectInputStream.readObject0(Unknown Source)
      at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
      at java.io.ObjectInputStream.readSerialData(Unknown Source)
      at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
      at java.io.ObjectInputStream.readObject0(Unknown Source)
      at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
      at java.io.ObjectInputStream.readSerialData(Unknown Source)
      at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
      at java.io.ObjectInputStream.readObject0(Unknown Source)
      at java.io.ObjectInputStream.readObject(Unknown Source)
      at hudson.remoting.UserRequest.deserialize(UserRequest.java:182)
      at hudson.remoting.UserRequest.perform(UserRequest.java:98)
      ... 9 more
      [TASKS] Skipping publisher since build result is FAILURE

          [JENKINS-10153] Regression issue in Warnings Plugin

          Ulli Hafner added a comment -

          Can you please check if this could be related with a non up to date slave.jar file on the slave?

          Ulli Hafner added a comment - Can you please check if this could be related with a non up to date slave.jar file on the slave?

          Maxim Abrashkin added a comment -

          I've got the same problem.
          And I can confirm that the problem is solved by updating slave.jar to last version.

          Is there any check of slave compatibility with master? It will be nice to report compatibility problem instead of some strange exception in build log.

          Maxim Abrashkin added a comment - I've got the same problem. And I can confirm that the problem is solved by updating slave.jar to last version. Is there any check of slave compatibility with master? It will be nice to report compatibility problem instead of some strange exception in build log.

          herve schnitzler added a comment -

          Yes, I confirm that the slave.jar was not up-to-date.
          Sorry for the false alert.
          I agree with Maxim that a compatibility check on the master would be really useful as the error message didn't quite tip me into thinking that was the issue.
          So this issue can be closed.
          Thanks.

          herve schnitzler added a comment - Yes, I confirm that the slave.jar was not up-to-date. Sorry for the false alert. I agree with Maxim that a compatibility check on the master would be really useful as the error message didn't quite tip me into thinking that was the issue. So this issue can be closed. Thanks.

          Ulli Hafner added a comment -

          Please vote for JENKINS-453

          Ulli Hafner added a comment - Please vote for JENKINS-453

            drulli Ulli Hafner
            herve herve schnitzler
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: