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

xunit hangs (on one particular slave) after upgrading Jenkins from 2.6 to 2.9


    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: xunit-plugin
    • Labels:
    • Similar Issues:



      I've recently updated Jenkins to 2.9 (from 2.6), including all slave.jars and all plugins with their most recent versions. All of suddenly, job started at one particular slave hangs at xunit processing, which worked OK so far.

      This is what I see in job console:
      Build step 'Conditional steps (multiple)' marked build as failure
      Archiving artifacts
      [xUnit] [INFO] - Starting to record.
      [xUnit] [INFO] - Processing Custom Tool
      [xUnit] [INFO] - [Custom Tool] - 1 test report file(s) were found with the pattern 'Reports\unpacked*_build-5481.rxlog.data' relative to 'c:\Jenkins\workspace\SecurexMonitoring' for the testing framework 'Custom Tool'.

      From time to time, the xunit processing finishes after unusually long period of time. But in most cases, I need to kill the job manually, because it blocks other jobs.

      Virtually the same works fine on two other slave machines. The only difference between the slaves is that the not-working one is located in different data center. But it was there also before. The response time of the problematic slave is around 150ms, so it should not be an issue either? Jenkins configuration should be the same on all three slaves.

      Once I kill the 'hanged' job, it throws this exception to master console:
      Jun 14, 2016 12:45:27 PM WARNING hudson.model.AbstractBuild$AbstractBuildExecution reportError
      Step ‘Publish xUnit test result report’ aborted due to exception:
      at java.lang.Object.wait(Native Method)
      at hudson.remoting.Request.call(Request.java:147)
      at hudson.remoting.Channel.call(Channel.java:780)
      at hudson.FilePath.act(FilePath.java:1007)
      at hudson.FilePath.act(FilePath.java:996)
      at org.jenkinsci.plugins.xunit.XUnitProcessor.performTests(XUnitProcessor.java:145)
      at org.jenkinsci.plugins.xunit.XUnitProcessor.performXUnit(XUnitProcessor.java:88)
      at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:142)
      at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:134)
      at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
      at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
      at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
      at hudson.model.Build$BuildExecution.post2(Build.java:185)
      at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
      at hudson.model.Run.execute(Run.java:1745)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
      at hudson.model.ResourceController.execute(ResourceController.java:98)
      at hudson.model.Executor.run(Executor.java:410)

      Any idea what could be the cause of this problem or what to try to fix it? Feel free to let me know if you need more details.

      PS: added slave thread dump




            • Assignee:
              gbois Gregory Boissinot
              odklizec Pavel Kudrys
            • Votes:
              0 Vote for this issue
              2 Start watching this issue


              • Created: